The ASP.NET team released Blazor WebAssembly 3.2.0 Preview 4 on the official blog as scheduled: https://devblogs.microsoft.com/aspnet/blazor-webassembly-3-2-0-preview-4-release-now-available / , At the same time, I sent a message on twitter to bring the following picture. This picture very vividly shows that Blazor Webassembly is preparing for the final launch. According to the development plan, Blazor WebAssembly 3.2.0 Preview will be released next week 4.23 5. Completing the development of functional features, the next step is to release Blazor WebAssembly 3.2.0 RC in early May. It will be officially launched at the 5.19 Microsoft Build conference and enter the front-end development journey using C #.
Blazor WebAssembly 3.2.0 Preview 4 new features:
- Access to the host environment during startup:
WebAssemblyHostBuilder通过IWebAssemblyHostEnvironment的HostEnvironmentthe details are disclosed in the properties and distinguished during the startup process in the application environment (development, staging, production, etc.). If the application is hosted in an ASP.NET Core application, the environment will reflect the ASP.NET Core environment, so ASP.NET Core is definitely the best development environment, after all, it is a pro son, and of course it is happy to be in other environments. No matter if you are using Java, PHP, NodeJs or go, Blazor can be used as a front-end framework with separate front-end and back-end, allowing you to write front-end logic using C #. - Logging improvements:
WebAssemblyHostBuilderALoggingtype of property is now exposedILoggingBuilderthat can be used to configure logging applications, similar to how you would configure ASP.NET Core applications to log on the server, that is, bring Microsoft.Extensions.Logging to the front end, One of the remaining configuration frameworks will wait until Preview 5 is released next week - Brotli precompression: When publishing Blazor WebAssembly applications, the highest level of Brotli precompression has been used to further reduce the size of the application and eliminate the need for runtime compression. ASP.NET Core hosted applications have seamlessly utilized these pre-compressed files. For standalone applications, you can configure the host server to redirect requests to pre-compressed files. Using pre-compressed files, the published Blazor WebAssembly is now 1.8MB, which is lower than the 2MB in the previous preview. The minimum application without Bootstrap CSS is reduced to 1.6MB.
- Loading assemblies and runtimes in parallel: Blazor WebAssembly applications can now load assemblies and runtimes in parallel, saving precious time in application loading time.
- Simplify the IL linker configuration of the application: The Blazor WebAssembly application provides a .NET IL linker configuration file to customize the linker's behavior
- Localization support: The Blazor WebAssembly application now supports localization using .NET resource files (.resx) and satellite assemblies.
- Get API documentation of various Blazor WebAssembly in smart tips
At present, the main problem with Blazor is debugging support. Although there are some developments in debugging support, there are still many limitations in the current debugging experience in Visual Studio and Visual Studio Code. We can see a lot of Debugger support issues in Mono's Webassembly development issues list https://github.com/mono/mono/milestone/17 :
Why does Blazor appear?
Modern browsers support WebAssembly. WebAssembly is a new encoding method that can run binary format files in modern web browsers, running at close to native performance. Blazor tried to use WebAssembly and Mono to bring .NET back to the browser. In addition to developing with C #, you can also run C # on the browser (using WebAssembly), so that we can use many dotnet APIs in the browser.
The Blazor documentation is relatively complete: https://docs.microsoft.com/zh-cn/aspnet/core/blazor/get-started , the official team is strengthening this document, there is an issue on github tracking https://github.com / dotnet / aspnetcore / issues / 20890 , everyone is welcome to participate.
At present, we are developing an open source project ant-design-blazor, the goal is to become a Blazor officially recognized by Ant Design and enrich the Blazor ecosystem. Now that we have just started, we need interested students to participate together.
Github: https://github.com/ElderJames/ant-design-blazor
Demo:
https : //ant-design-blazor.gitee.ioDevelopment
documentation:
https://github.com/ElderJames/ant-design-blazor / wiki
Blazor documentation: https://docs.microsoft.com/zh-cn/aspnet/core/blazor/?view=aspnetcore-3.1
Any form of issue and PR are welcome