Blazor, a new framework for browser-based .NET apps
summary
Blazor runs .NET in the browser by loading a mono runtime compiled to WebAssembly (mono.wasm) and app assemblies — first-load network is about mono.wasm 2.3 MB first-load and drops to ~15.5 KB cached on repeat views. The framework provides component-based UI, DI, router, JS interop, C# source-level debugging in browser devtools, built-in JWT auth/authorization, data annotations validation, and static content in class libraries. Deployment options include client-side and server-side models (SignalR updates), PWA, Electron sample, and a Flutter renderer demo.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 2:53Blazor Basics
- 7:55Blazor WebAssembly
- 10:35Browser Demo
- 16:52Mission Control
- 21:04Authentication Authorization
- 24:57Login Display
- 29:29Validation
- 34:29Component Libraries
- 34:49Reusable Component Libraries
- 35:34Creating a Blazor Component
- 41:39Serverside Blazor
- 43:04Car Buyer
- 47:29Pros and cons
- 49:44More Blazor options
- 50:34Blazor clientside
- 52:00BlazorPWA
- 53:06Electron
- 54:57Flutter
related talks
01h 03mBlazor, a new framework for browser-based .NET apps
41mBlazor, a New .NET Single Page Application Framework
01h 01mBlazor, a new framework for browser-based .NET apps
01h 01mBlazor: Modern Web development with .NET and WebAssembly
58mBlazor: C# running in the browser via WebAssembly
09mBlazor with WebAssembly
46m.NET: What's Blazor - Front .NET
56mASP.NET Blazor—the C# Angular or the return of Silverlight?
