ASP.NET Update: Blazor WebAssembly 3.2.0 Released
The Blazor WebAssembly Release Candidate (RC) that includes all the breaking improvements and amazing features is right here. Custom boot resource loading and API referencing docs are the two important features in this release. But before going deeper, let’s take an overview of Blazor and WebAssembly.
Blazor: ASP.NET Feature
Blazor can execute client-side C# code in their browser with WebAssembly. Moreover, it is a real .NET executing and running on WebAssembly, enabling the users to re-use the code, tools or libraries again and again from the server-side parts of the application. And not only this, Blazor allows user to execute client logic on the server as well. The environment of real-time messaging infrastructure can be implemented by sending client UI events back to the server mode, using SignalR. After the execution on the server-side, all the necessary changes related to UI are then transferred to the client and fused into the Direct Object Model (DOM).
Some other leveraging characteristics of Blazor WebAssembly are as follows;
- Potential to analyze the productivity of C# and runtime typing
- It follows the steady and established .NET ecosystem
- It shares the component model with Blazor server applications
- Developers can build apps as a standalone static site or host with ASP.NET Core
- Complete support for authentication, globalization and localization
- Deployment of PWA (Progressive Web Applications) with offline features and native OS assimilation
- Configuration of app based on the environment
- Full-stack debugging
- IL (Intermediate Language) trimming
- Build-time precompression
WebAssembly 3.2.0 Updates
A Senior Program Manager on the ASP.NET team at Microsoft, Daniel Roth, stated two exclusive features in the WebAssembly 3.2.0 Updates;
Custom Boost Resource Loading:
- To load static resources, including time zone data from a CDN
- To load compressed assemblies while using an HTTP request and then decompressed these assemblies on the client-side. It helps those hosts that don’t support or fetch compressing contents from servers.
- Code-named resources to a changed name by readdressing each fetch request to a new one.
API Reference Docs:
The documentation of API for Blazor WebAssembly namespaces are now accessible from .NET API browser as a part of the ASP.NET Core 3.1 API documentation.
All the five previews of Blazor WebAssembly enhance client-side apps performance, enables improved integrations with Visual Studio and updates IntelliSense documentation. According to Roth, all the important changes and features have been released till now and no further alterations are required at this point, meaning that all the productions of Blazor WebAssembly are ready!
Similar Posts by The Author:
- Why Enterprises Must Integrate Big Data Analytics with .NET Development?
- How to Choose the Right AWS Cloud Storage for Your Data?
- Five Things You Should Know About .NET 5
- Ansi ByteCode is recognized by Techreviewer as a Top Software Development company in 2020
- How ASP.NET/MVC Can Meet Your Website Development Requirements