1. Faster Startup and Asset Loading
One of the most noticeable improvements in Blazor for .NET 10 is the dramatic reduction in startup time , particularly for Blazor WebAssembly applications. Historically, Blazor WebAssembly apps required downloading relatively large framework and library files before they could run, which sometimes created friction compared to JavaScript frameworks.
Enhancements in .NET 10
Static Assets with Fingerprinting and Compression: Scripts and framework files are now served as precompressed and fingerprinted static assets . This allows browsers to aggressively cache them and reuse them across sessions or even different apps.
Preloading Support: Developers can now preload Blazor’s JavaScript and WebAssembly assets via <LinkPreload /> , reducing the "time-to-interactive."
Native AOT Benefits: Ahead-of-time compilation reduces payload size and improves execution speed on WebAssembly.
Impact: Applications feel more responsive and interactive, even on low-bandwidth or mobile connections, making Blazor WebAssembly far more competitive with SPA frameworks like React and Angular.
2. Persistent Component State
Blazor Server and Blazor WebAssembly both face challenges when it comes to maintaining state across app lifecycle events such as page reloads , reconnections , or pre-rendering scenarios . Asp.Net Core 10 introduces persistent component state to solve this problem.
What it does
Components can now persist their state (e.g., form input, UI context, filters) across page reloads and server reconnects.
State can be preserved not only in memory but also serialized for persistence between user sessions.
Impact: This eliminates frustrating experiences where a user refreshes the browser and loses their progress. For server-side Blazor apps, this also makes reconnection scenarios far smoother.