Blazor: C# running in the browser via WebAssembly
summary
Blazor runs C# in the browser via WebAssembly using the Mono runtime, loading DLLs in the browser and shipping an initial payload of about 2.4 MB; demos show HTTPClient calls to a shared WeatherForecast model, a localStorage-backed todo that uses C# wrappers instead of JavaScript, an Electron desktop build that runs the same UI, and a server-side mode that streams updates over SignalR. Tooling and ahead-of-time compilation are still preview quality, suitable for hobby or internal apps but not yet a drop-in enterprise bet.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:35Current State of the SPA Front End
- 4:06At the end of the day
- 4:28Problems
- 7:32What is Web Assembly WASM?
- 31:39Rapid Fire Questions
- 33:16How does Blazor work?
- 34:16Why Mono? Why not.NET Core?
- 43:41Blazor 3 party Components
- 44:06Current Status - What's there?
- 45:42Current Status - What's coming?
related talks
01h 01mBlazor: Modern Web development with .NET and WebAssembly
09mBlazor with WebAssembly
41mBlazor, a New .NET Single Page Application Framework
59mBlazor, a new framework for browser-based .NET apps
01h 03mBlazor, a new framework for browser-based .NET apps
36mGoodbye client side JavaScript, Hello C#'s Blazor
01h 01mBlazor, a new framework for browser-based .NET apps
56mASP.NET Blazor—the C# Angular or the return of Silverlight?
