@EngincanV When wiull it be fixed for Blazor WASM? Its a big deal not having this.
Has this been fixed in v5?
What about impersonation for for Blazor WASM?
@Albert - Thanks. The first issue is having to redirect from the website that is created by the app, then to the login page. This also happens when the user logs off. It goes to the website (we dont use that), and then redirects to the login page.
We want users to be able to go straight to the login page.
when will v4.3 patch be released and what is fixed for commercial over what shown in github?
v4.3.2 comes Fiday.
@Albert - Thanks for the date on v4.3.2, where can we see what will be fixed/released in the Commercial version?
Github only shows what is in the open source version.
when will v4.3 patch be released and what is fixed for commercial over what shown in github?
The main problem is the information in the error message is not helpful.
so that is the first thing to resolve.
We do not want to download and edit source as that will then be a problem when we have to upgrade eg 4.3 patch.
bump
@liangshiwei Thanks, we'll try that I really hope you can get this framework faster, we would have to change lots of things to migrate back to a Server. I already discussed that in a different question and Alpers said we had to create a brandnew tenmplate and t5hem migrate the whole app piece by piece over...
@liangshiwei - As you know the Blazor WASM is dreadfully slow to load. It takes 10+ seconds. The user experience is made worse by having to go to the index page. GTMetrix even times out on the first page load time!
How do we;
We also dont want to have to mess with the module source code for something so obvious as that then breaks the ability to easily upgrade.
Really appreciate your help here, these are basic and reasonable requirements for a framework.