Hi,
Does the problem still exist?
I'm checking
Hi,
On top of this everything is performing super super slow (in debug mode..). I see that for every refresh there is a 39.97 MB download.. is the auto part not working? Should WASM not be an opt-in and not a default?
The freeze happened during the mode change from the Balzer server to the Blazor wasm.
This is the design of blazer-web app.
If you open the console panel of the browser, you will see the output messages of wasm initializing.
See: https://github.com/dotnet/aspnetcore/issues/52154
According to your documentation you have you have updated server and wasm projects to use this new .net 8.0 thing But why have you then also added this Blazor Web App option in Suite?
There are three different modes,
InteractiveServerRenderMode. -> Blazor server template InteractiveWebAddemblyRenderMode -> Blazor webassembly template InteractiveAutoRenderMode -> Blazor webapp template
You can check Microsoft's documentation
https://learn.microsoft.com/en-us/aspnet/core/migration/70-80?view=aspnetcore-8.0&tabs=visual-studio#update-a-blazor-webassembly-app https://learn.microsoft.com/en-us/aspnet/core/migration/70-80?view=aspnetcore-8.0&tabs=visual-studio#convert-a-blazor-server-app-into-a-blazor-web-app
Hi,
You can upgrade to 8.2.0.
We released a stable version yesterday
Hi,
We have an example: https://github.com/abpframework/abp-samples/tree/master/ConcurrentLogin
This is not an error and it's not code in the template.
I think one of your coworkers added the code for diagnostics, but forgot to remove it.