Component-based C# and Razor Programming in Blazor
summary
Blazor runs C# Razor on WebAssembly (and a server-side flavor) so UI code and components use C#, Razor and Bootstrap instead of TypeScript or JSX; client-side startup currently downloads Mono and many DLLs taking >10s initial download but team focuses on performance. Server-side Blazor uses SignalR proxy for UI diffs and is slated to ship with .NET Core 3.0; client-side uses HttpClient to fetch JSON, IJSRuntime for optional JavaScript interop, and a component model (table grid, autocomplete) that already renders and binds data.
AI-written summary · about
chapters (9)
- 0:00Introduction to Blazor
- 2:30How Blazor works
- 6:36Blazor vs. Silverlight
- 9:31Project infrastructure
- 13:44Project types and setup
- 20:11Server-side Blazor demo
- 33:59Client-side Blazor demo
- 38:29Custom components
- 43:59JS interop and conclusions
related talks
46m.NET: What's Blazor - Front .NET
01h 00mASP.NET Blazor programming 101
01h 03mBlazor, a new framework for browser-based .NET apps
01h 03mIntroducing Razor Components in ASP.NET Core 3.0
56mASP.NET Blazor—the C# Angular or the return of Silverlight?
58mWelcome to Blazor
01h 01mBlazor: Modern Web development with .NET and WebAssembly
58mIntro to Blazor, WebAssembly and Razor in .Net
