Blazor for Web Form and C# Developers
summary
Shows a concrete migration path from ASP.NET Web Forms to Blazor by extracting business logic into a .NET Standard class library, running UI on Blazor Server (SignalR) or WebAssembly, and replacing ListView/master pages with Razor components. Demonstrates a working sample app called Shop on Blazor repo, plus an experimental Blazor WebForms components shim that accepts pasted ASPX-like markup, compiles, and renders the same HTML without viewstate; runs on .NET Core 3.1 and interoperates with JavaScript.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:16What is Blazor?
- 2:26Blazor versus Web Forms
- 3:37Blazor architectures
- 5:31Choosing a hosting model
- 7:17Comparing paradigms
- 9:36Migration challenges
- 12:14Initial migration demo
- 13:44Analyzing legacy code
- 16:44Blazor application structure
- 19:12Web Forms demo
- 21:00Blazor code review
- 23:33Migration requirements
- 26:20Advanced migration steps
- 27:19Using .NET Standard
- 30:53Blazor Server demo
- 32:21Custom components
- 33:47Blazor experimental controls
- 35:35Demoing shim components
- 38:17Resources and wrap-up
- 39:44Q&A session
related talks
01h 01mBlazor, a new framework for browser-based .NET apps
01h 01mBlazor, a new framework for browser-based .NET apps
18mBlazor Is Web Technology with C# and .NET Core
53mCreating Next-Generation Applications with Blazor
01h 00mASP.NET Blazor programming 101
01h 13mBlazor: SPAs in the Browser with C# and WebAssembly
58mIntro to Blazor, WebAssembly and Razor in .Net
41mModern Full-Stack Web Development with ASP.NET Core & Blazor