Blazor United prototype
Why Stack Overflow recommends it
Stack Overflow users link it as the original source for how Blazor United and the .NET 8 auto render modes were meant to work, both in answers and when asking how to enable it.
Recommended by 1 people across 1 different months, 2023 to 2025.
What it is
A 13-minute prototype demo by Steve Sanderson, the original creator of Blazor, showing experiments considered for Blazor in .NET 8, later known as Blazor United. It shows server-side rendering, WebAssembly and server interactivity combined in one stack using dual target frameworks.
What people said
Recommends James Gray · 2023-11 · Stack Overflow · on “Is Blazor United going to replace WASM and server”
Per the demo video: [this video] It's not replacing them so much as letting you use both of them with the same architecture and the server+client communication will determine which one it needs at the moment. It does this by having you use 2 target frameworks at the same time on build. In the video the used net8.0;net7.0-browser (important to note that this was 9 months ago and was still in prototype phase, I'm sure you would target .net v8 instead of v7 for the browser now). On first page load, when the WASM files haven't been cached yet, everything will operate with SSR, then on next page load, if the WASM has cached, WASM will take over. You can also forcibly control globally or per component
Cites Mohammad Komaei · 2023-02 · Stack Overflow · on “How to enable blazor united on a blazor wasm project?”
Based on this video [this video] there is a feature called Blazor United. Blazor United is a prototype project from Steve Sanderson, the original creator of Blazor, which combines the advantages of Razor Pages, Blazor Server, and Blazor WebAssembly into a single stack. The prototype is currently in development and is expected to be included in .NET 8. Some of the features of the prototype include support for traditional server-side rendering, WebAssembly, and WebSockets. Additionally, the prototype includes features such as hot module reloading, lazy loading, and prerendering. The project is still in its early stages, and more features and improvements are expected to arrive in the future. How to
Cites Matin · 2023-11 · Stack Overflow · on “How does Auto Render mode work in Blazor .NET 8?”
I've been experimenting with Blazor in .NET 8 and I'm trying to understand how the Auto-render mode works. From what I've learned, Blazor initially uses a WebSocket connection in Auto mode to provide interactivity via server-side rendering. Then, it switches to WebAssembly (WASM) when the WASM resources are loaded in the background. However, in my tests, I've noticed that there's no interactivity available until the WASM resources are fully loaded. In the network tab of my browser, I can see a WebSocket connection, but it seems like the UI is just prerendered and not interactive. I've also learned that components that are going to be rendered in WASM should be placed in the ProjectName.Clien
Cites Oleksii Kyslytsyn · 2025-08 · Stack Overflow · on “Blazor SSR with EditForm, the EditForm model has a list of objects. How can user update a field in one of the objects in the list?”
And this rendering mode as WASM in Blazor for is pretty similar to remote/local repositories for example in Apache Maven. [this video]