Microsft announced the Blazor WebAssembly 3.2.0 Release Candidate, which contains all of the features and improvements that you can expect to release for the upcoming Blazor WebAssembly release.

This release brings Custom boot resource loading and API reference docs.

Starting with this release, developers can now customize how the boot resources are loading using the loadBootResource API. This API enables developers to make any needed modifications to how these specific outbound requests are constructed.

For instance, if you want to load some of the resources from an external CDN. Although Microsoft does not currently host the Blazor framework files on any specific public Content Delivery Network (CDN), developers are unrestricted to add them to their own CDN if they wish.

3.2 RC also brings API reference docs. API reference docs for the Blazor WebAssembly namespaces are now available in the .NET API browser as part of the ASP.NET Core 3.1 API docs.

Microsft said that when publishing a ASP.NET Core hosted Blazor WebAssembly app using Visual Studio, satellite assemblies from the client application do not get copied to the publish folder. This issue will be addressed in the upcoming release. For now, you can choose to publish the app from the command line using dotnet publish.

#blazor #webassembly #dotnet #asp-net