-
ABP Framework version: v7.1
-
UI type: Blazor WASM
-
DB provider: EF Core
-
Tiered (MVC) or Identity Server Separated (Angular): MVC
Hi,
We are upgrading an app to v7.1 template.
The performance on v7.1 is worse than previous versions. Our application is not very big.
What steps can we take to improve the loading speed at startup and user experience?
-
We do not want to use the ABP “default” public website. We just want users to go to our login URL and open the login page. Currently it takes forever to load the web app, then redirect users to the login page. It is a real pain for users!
-
After logout the user should be redirected DIRECTLY to the login page. They should not have to load the abp website, then redirect to login again.
Thanks. Andrew
3 Answer(s)
-
0
See:
https://support.abp.io/QA/Questions/4645/Blazor-wasm-application-hang-after-login
, https://support.abp.io/QA/Questions/4748/Redirect-to-login-page-after-logout
and https://support.abp.io/QA/Questions/1152/How-to-to-Login-page-when-accessing-the-app-and-after-logout#answer-5c9c7a51-3689-9ec8-e5b6-39fbc698d514The situation is still the same.
-
0
Why can't this be fixed? should we create a github issue?
-
0
Hi,
Because Blazor web assembly needs to load all DLLs at the first time. We can do nothing,
You can see many discussions about Blazor wasm:
https://www.reddit.com/r/Blazor/comments/y0w90j/blazor_wasm_terrible_performance_score/maybe the Blazor server is more suit for you.
