Blazor: Modern Web development with .NET and WebAssembly
summary
Blazor runs real .NET in the browser by shipping a mono.wasm runtime plus your compiled DLLs and boots via a tiny JavaScript shim; a simple sample downloads about 1.8 MB compressed today and executes C# components, routing, dependency injection and HTTP calls (HttpClient uses the browser fetch API via JavaScript interop). Debugging is an early Chrome remote proof‑of‑concept, and there’s an alternate server-side via SignalR (Razor Components) hosting model that keeps execution on the server for fast startup and full .NET library support.
AI-written summary · about
chapters (28)
- 0:00Start
- 0:52Web Assembly
- 1:34Advantages for Using Dotnet for Full Stack Web Development
- 5:55Create a Web Application
- 8:02Functions Block
- 8:41Index Page
- 9:15Counter Component
- 11:15Fetch Data Component
- 13:40Route Component
- 13:57Router Component
- 14:56Network Traffic
- 17:20Debugging
- 18:23Remote Debugging
- 20:52Publishing
- 29:48Javascript Interop
- 32:01Sync Task
- 34:28Community Package
- 34:51Blazer Extensions Storage Library
- 36:06Storage Api
- 38:46Component Implementations
- 40:43Sample Application
- 53:34Debug
- 55:10Startup Class
- 56:53Razer Components
- 57:14Templated Components
- 57:29Demo Template Components
- 58:41Template as a Child Element
- 1:00:18Additional Resources
related talks
01h 03mBlazor, a new framework for browser-based .NET apps
58mBlazor: C# running in the browser via WebAssembly
41mBlazor, a New .NET Single Page Application Framework
09mBlazor with WebAssembly
59mBlazor, a new framework for browser-based .NET apps
46m.NET: What's Blazor - Front .NET
58mIntro to Blazor, WebAssembly and Razor in .Net
36mBlazor - Full Stack Web Development in C# Only