A fistful of Blazor; Its .NET in the browser
summary
Blazor claims you can write SPA UI in C# that runs on Mono over WebAssembly (not by compiling C# to WASM). Demoed components, three component styles, lifecycle hooks, two‑way binding, routing with parameter constraints, dependency injection and HttpClient (backed by the browser Fetch API), plus NuGet packages like Markdig and Serilog loaded into the browser DLLs. Built a markdown viewer and a login modal that work, and used JS interop for geolocation and DOM focus. Rough edges: large DLL payloads, weak debugging, no route guards, opaque ElementRef and CSS scoping problems.
AI-written summary · about
chapters (7)
- 0:00Start
- 38:27use the uri helper inline
- 39:45put constraints on those parameters
- 54:01provide an action parameter on your component
- 55:48create a component library
- 57:35grab a reference to your component
- 59:06inject style directly into your component
related talks
01h 03mBlazor, a new framework for browser-based .NET apps
09mBlazor with WebAssembly
01h 01mBlazor: Modern Web development with .NET and WebAssembly
01h 00mASP.NET Blazor programming 101
01h 01mBlazor, a new framework for browser-based .NET apps
01h 01mBlazor, a new framework for browser-based .NET apps
36mBlazor - Full Stack Web Development in C# Only
59mThe future of Web: what Microsoft Blazor can do for you
