Earlier this week, Microsoft released Blazor WebAssembly 3.2 RC. This is the last planned preview release of Blazor WebAssembly, and it contains all features expected for its official general availability. The production-ready release is scheduled for sometime in May.
Blazor is a new framework in ASP.NET Core that allows developers to create interactive web applications using C# and HTML. Blazor WebAssembly allows single-page applications to run in the client's web browser using a WebAssembly-based .NET runtime. Being client-side, it supports scenarios involving progressive web applications (PWAs) and offline applications using the client's resources.
The first preview for Blazor WebAssembly 3.2 was released at the end of January. Since then, the following preview releases followed a steep schedule, with the fifth preview being released just last week. One of the two features exclusive to this release is custom boot resource loading, which allows the developer to customize how to load the required boot resources from the server. The second new feature is the inclusion of API reference documentation for the Blazor WebAssembly namespaces.
According to Daniel Roth, program manager for the ASP.NET team at Microsoft, there shouldn't be any new features from this point onwards:
This release contains all of the features and improvements that we expect to release for the upcoming Blazor WebAssembly release. It consolidates features aimed at increasing the performance of client-side applications, better integration with Visual Studio, and updated IntelliSense documentation - all from the past five preview releases. There are no more breaking changes planned at this point.
Despite being close to the final product, there are still some issues to be solved before Blazor WebAssembly's official release. All pending issues can be found in the official project board at GitHub. The current release candidate requires .NET Code SDL 3.1.201 or later. Microsoft also recommends installing the latest preview of Visual Studio 2019 16.6.