Hi. I am new to blazor and I think .NET 8 blazor gives so many options. I think about combining Blazor Server with Web API (written in clean architecture), everything works on server and I think that the architecture is so simply: only one project for Blazor and then fetch data from API project controllers.
I don't get the question. In the future, Blazor United will allow you to use server-side rendering for Blazor web apps. Right now, when you use WebAssembly, it will always download the whole app before running it, as far as I understand.
You should prevent this error from happening. When this error shows up, your application stops working and cannot be used anymore. I don't know if you can stop the message from appearing, but I can tell you that it most likely is not what you want to do.
is the biggest similarity between 2 that your whole page does not refresh like old fashioned full page server trip. i am new so plesse advise if iam correct.
Both, Blazor Server and Blazor WebAssembly provide a single-page experience where the page does not require a full page reload to rerender parts of the application. With .NET 8, you also have static server content as the third option. WebAssembly fully renders on the client and does not require ASP.NET Core on the server.
