- ABP Framework version: v4.4
- UI type: Blazor Web Assembly
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): no
- Exception message and stack trace:
- Steps to reproduce the issue:"
I see that the default template generated by ABP Suite for Blazor WebAssembly app is not really using Blazor components to display account module. For example if I navigate to "My Account" page it loads the whole HTML from the server thus the page is MVC and not part of Blazor wasm. Same for login form. They are serverd from the different port (.HttpApi Host project).
I also tested with Blazor server side template and same results -> My Account is not part of blazor but seems to be MVC page. When switching pages between "my account" and "home" page I can see that when navigating to "home" page it will always initiate SignalR hub which indicates to be that it is the inital call to the server-side blazor.
However based on your website (https://commercial.abp.io/modules/Volo.Account.Pro) it says that Account module also supports Blazor UI Framework. Does it support both wasm and server side? How can I take it into use?
5 Answer(s)
-
0
Hi @petri.uusitalo
This is by design. And this is also same for Angular UI, even same for tiered MVC projects. You are redirected to MVC UI of .HttpApi.Host project for login.
However based on your website (https://commercial.abp.io/modules/Volo.Account.Pro) it says that Account module also supports Blazor UI Framework
This doesn't mean Account module doesn't support Blazor/Angular UI.
-
0
Could you be more specific. Which views/pages are supported in Blazor in account module? Is "My accont" page supported?
-
0
Hi,
Only the setting contributor page is on Blazor UI. For other pages, you are redirected to Host MVC UI.
-
0
OK, thanks. Is there any plan to implement also Blazor UI for other pages in a near future?
-
0
As i said, this is by design. So don't expect it to be changed in future.
