Blazor - Full Stack Web Development in C# Only
summary
Blazor explains how C# runs both client and server: the browser mode uses Blazor WebAssembly by compiling the Mono runtime to WebAssembly so .NET DLLs execute in-browser (demo shows debugging in Chrome only), and the server mode uses Blazor Server with SignalR DOM diffs—server keeps components in memory and sends UI updates via RPC. Mixed hosting shares models between client and server. Current tradeoffs: no direct C#→WASM compiler yet, initial payload around 5.4MB (about 2.4MB compressed), server CPU and connection load vs thin client.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 2:10Problem
- 4:23Blazor Basics
- 6:21Blazor syntax
- 7:14Hosting models
- 7:58Blazor represent
- 8:38WebAssembly
- 10:34Assembly Language
- 11:20Browser Support for WebAssembly
- 12:09Mono
- 14:14Web Assembly
- 16:22Blazor Demo
- 18:18Browser Demo
- 19:26Debugging
- 19:47Magic Key
- 20:12Experimental Debugging
- 21:38Demo
- 22:47Blazor Server
- 23:27SignalR
- 24:03Remote Procedure Calls
- 25:34Remote Procedure Demo
- 26:58Advantages and Disadvantages
- 27:31Blazor WebAssembly
- 29:21Performance
- 30:22Current State
- 30:58Alternatives
- 31:17Questions
related talks
01h 01mBlazor: Modern Web development with .NET and WebAssembly
46m.NET: What's Blazor - Front .NET
01h 00mASP.NET Blazor programming 101
01h 03mBlazor, a new framework for browser-based .NET apps
09mBlazor with WebAssembly
58mWelcome to Blazor
59mThe future of Web: what Microsoft Blazor can do for you
58mIntro to Blazor, WebAssembly and Razor in .Net
