The Blazor Multiverse: get to know the different Blazor frameworks
summary
Covers Blazor WebAssembly, Server, United (Blazor Web App), Hybrid and Mobile Bindings with concrete tradeoffs: Blazor Server uses SignalR and keeps state/server-side code but forces round trips; Blazor WebAssembly downloads the .NET runtime to the browser (demo shows runtime files downloading) and works offline but exposes client code; Blazor Web App (net8+) lets per-component interactive auto mode or stream rendering (100 ms startup check, stream updates), Visual Studio templates create server/client projects, Hybrid embeds Blazor in .NET MAUI webviews and works for desktop/mobile, Mobile Bindings are community‑maintained. Recommends migrating Server to Web App for net8+, choose render mode per component for flexibility.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:43What is Blazor
- 8:43Blazor Server
- 11:54Blazor WebAssembly
- 14:04Blazor United
- 18:28Blazor Hybrid
- 22:42Blazor Mobile Bindings
- 25:10Project structure
- 36:58Live demo: render modes
- 44:17.NET 9 features
- 48:56Resources & closing
- 50:01Q&A
related talks
46m.NET: What's Blazor - Front .NET
58mWelcome to Blazor
01h 01mBlazor, a new framework for browser-based .NET apps
36mBlazor - Full Stack Web Development in C# Only
01h 01mBlazor, a new framework for browser-based .NET apps
01h 03mBlazor, a new framework for browser-based .NET apps
58mIntro to Blazor, WebAssembly and Razor in .Net
51mComponent-based C# and Razor Programming in Blazor
