The future of Web: what Microsoft Blazor can do for you
summary
Blazor runs C# in the browser via WebAssembly and shows both client-side WebAssembly and server-side SignalR hosting models, requires .NET Core 3.x and recent Visual Studio, and can reuse existing .NET libraries. The demo builds components, manipulates the DOM from C# and calls JavaScript back and forth, even 500 forms generated instantly to illustrate speed. Offline use works after download, debugging is limited, and SignalR connection limits constrain server-side scaling.
AI-written summary · about
chapters (14)
- 0:00Introduction and background
- 2:19Evolution of web technology
- 5:02Understanding WebAssembly
- 8:24Limitations of JS frameworks
- 11:54Architecture and components
- 14:02Benefits of Blazor
- 17:00Blazor vs. Silverlight
- 21:24The case for Blazor
- 25:58Client vs. server hosting
- 29:00Demonstration and syntax
- 35:47DOM interaction and APIs
- 41:48JavaScript interoperability
- 47:26Pros and cons of Blazor
- 51:49Q&A and conclusion
related talks
01h 00mASP.NET Blazor programming 101
46m.NET: What's Blazor - Front .NET
01h 01mBlazor, a new framework for browser-based .NET apps
56mASP.NET Blazor—the C# Angular or the return of Silverlight?
01h 01mBlazor: Modern Web development with .NET and WebAssembly
36mBlazor - Full Stack Web Development in C# Only
58mIntro to Blazor, WebAssembly and Razor in .Net
01h 03mBlazor, a new framework for browser-based .NET apps