Old to Gold: How to Modernize Your Legacy ASP.NET Apps Gradually
summary
Shows an end-to-end incremental migration: upgrades a legacy MVC site by converting a class library to .NET Standard 2.0, scaffolding a side‑by‑side ASP.NET Core app on .NET 8, and wiring a YARP reverse proxy catch‑all to forward unresolved routes to the old app. Demonstrates adding Microsoft ASP.NET Core system.web adapters to preserve HTTPContext behavior, and uses the .NET Upgrade Assistant (v0.5) which automates many steps but leaves small manual fixes; YARP (v2.3) and adapters work in production.
AI-written summary · about
chapters (15)
- 0:00Legacy ASP.NET migration intro
- 3:54Framework vs modern .NET
- 9:37Strangler fig approach
- 12:03Reverse proxies in migration
- 15:13YARP as reverse proxy
- 19:28Why YARP for migrations
- 21:59YARP use cases beyond migration
- 25:06.NET Upgrade Assistant intro
- 29:00Live demo: legacy class library
- 33:38Migrating ASP.NET with YARP
- 42:37Web app migration steps
- 48:41Next steps after migration
- 56:24Handling system.web dependencies
- 57:49Migration tooling state and plans
- 58:10Q&A
related talks
01h 04mMigrate Your Legacy ASP.NET Projects to ASP.NET Core Incrementally with YARP
01h 03mTales from the .NET 8 Migration Trenches
44mModernize your ASPNET based systems using the Strangler Fig pattern
11mThe monster under the bed - working with legacy code
01h 02mSolid ASP.NET Core
46mWhat's New in ASP.NET Core 8 and Blazor 8
50mClean Architecture with ASP.NET Core 2.2
44mFrom Legacy to Vue.js
