I created the Blazor WASM (Abp Commercial v.8.3.2) solution with Abp Studio, but the structure is more like a Blazor WebApp, with the Blazor Client included in the project Blazor (blazor hosted). This doesn't allow me to use hot reloads and debug with "Edit and continue" option. Since the application has grown to over 180 entities with their associated management pages, both loading and, especially, debugging have become extremely slow, significantly slowing down development times. I'd like to set up the solution to have a single Blazor WASM project to ensure acceptable development times, be able to use hot reloads and debug individual pages.
How can I do this?
Thanks
32 Answer(s)
-
0
I created the private GitHub repository and sent you the invitation.
Thanks
-
0
Thanks I will check it asap.
-
0
hi
I have opened the PR to convert your project to WASM.
You can review and test it.
https://github.com/RobertoFiocchiMCSI/Cdi.Grc.AbpSupport/pull/1
Thanks.
-
0
I looked at the PR and it seems to work. I'm still having issues with hot reloading, but I think it's due to factors outside of the ABP.
Do you have any suggestions on how to make debugging more efficient?
Thanks
-
0
hi
I don't have much to suggest, Microsoft's documentation basically covers it all.
Thanks.
-
0
Ok, thanks anyway for your support
-
0
👍
