Migrate Your Legacy ASP.NET Projects to ASP.NET Core Incrementally with YARP
summary
Shows an incremental Strangler Fig migration using YARP as an in-app reverse proxy, converting a legacy MVC site into an ASP.NET Core facade that forwards unknown routes to the old app. Uses .NET Upgrade Assistant to move a class library to netstandard2.0 (14 steps in ~11s) and scaffold a Core MVC app with YARP (6 stages in ~7s). Adds Microsoft.AspNetCore.SystemWebAdapters and LigerShark for bundle parity, requires a few manual fixes but the proxyed setup works end-to-end.
AI-written summary · about
chapters (15)
- 0:00The legacy application challenge
- 1:44Migration strategies overview
- 7:17Understanding reverse proxies
- 10:14YARP and incremental migration
- 14:45How YARP works
- 17:28Why choose YARP
- 20:00The .NET Upgrade Assistant
- 21:49Live migration: Class library
- 29:05Live migration: Setting up YARP
- 34:57Live migration: MVC project
- 40:34Handling system.web dependencies
- 42:23Live migration: Moving controllers
- 47:23Fixing assets with LigerShark
- 52:04Advanced System.Web adapters
- 56:51Tooling status and Q&A
related talks
01h 00mOld to Gold: How to Modernize Your Legacy ASP.NET Apps Gradually
44mModernize your ASPNET based systems using the Strangler Fig pattern
01h 03mTales from the .NET 8 Migration Trenches
01h 02mSolid ASP.NET Core
56mWriting simpler ASP.NET Core
46mWhat's New in ASP.NET Core 8 and Blazor 8
50mClean Architecture with ASP.NET Core 2.2
01h 02mImplementing the Clean Architecture in .NET Core