|
Blazor WebAssembly
|
|
|
|
When the Blazor WebAssembly app is created for deployment without a backend ASP.NET Core app to serve its files, the app is called a standalone Blazor WebAssembly app.
|
|
When the app is created for deployment with a backend app to serve its files, the app is called a hosted Blazor WebAssembly app.
|
|
A hosted Blazor WebAssembly app typically interacts with the server over the network using web API calls or SignalR.
|
|
|
Advantages:
|
|
There's no .NET server-side dependency. The app is fully functioning after it's downloaded to the client.
|
|
Client resources and capabilities are fully leveraged.
|
|
Work is offloaded from the server to the client.
|
|
The .NET code of a Blazor Server application runs on the server-side. It means that the .NET code remains on the server and will not be sent to the client. Therefore, business logic cannot be decompiled, and your sensitive business algorithms cannot be analyzed.
|
|
An ASP.NET Core web server isn't required to host the app. Serverless deployment scenarios are possible, such as serving the app from a Content Delivery Network (CDN).
|
|
|
|
|
|
Limitations:
|
|
The app is restricted to the capabilities of the browser.
|
|
Capable client hardware and software (for example, WebAssembly support) is required.
|
|
Download size is larger, and apps take longer to load.
|
|
NET runtime and tooling support is less mature. For example, limitations exist in .NET Standard support and debugging.
|
|
|
All source of information collected from learn Microsoft Documentation page.
|
No comments :
Post a Comment