Blazor - Next Generation UI with .NET 6
summary
Blazor runs .NET in the browser via WebAssembly or on the server via SignalR, showing concrete tradeoffs: Blazor WebAssembly enables offline PWAs and ships DLLs (demo loads ~8.6 MB into browser cache), while Blazor Server keeps IP on the server for thin clients. Demos include Doom/Diablo ports, a Blazing Pizza storefront, and a hat-collection site wired to Azure Functions; .NET 6 adds hot reload and claims up to 20x faster decode than JS, and the examples compile, run and update live.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:33WebAssembly
- 7:50WebAssembly Demo
- 11:37How Blazor Works
- 13:05Clientside Web UI
- 14:03Blazor Web Assembly
- 17:05Getting Started
- 17:57Creating our first Blazor application
- 19:09Testing the Blazor application
- 21:52dlls
- 26:39Survey Prompt
- 28:37Parameter
- 33:19Demo
- 37:22Hat Collection
- 44:09Question
related talks
46m.NET: What's Blazor - Front .NET
01h 01mBlazor, a new framework for browser-based .NET apps
01h 01mBlazor: Modern Web development with .NET and WebAssembly
01h 03mBlazor, a new framework for browser-based .NET apps
01h 01mBlazor, a new framework for browser-based .NET apps
01h 01mWhat’s next for Blazor, and .NET on WASI
36mBlazor - Full Stack Web Development in C# Only
59mThe future of Web: what Microsoft Blazor can do for you
