Tales from the .NET 8 Migration Trenches
summary
Migrates a 15‑year ASP.NET 4.8 MVC5 app to .NET 8 incrementally using the system.web adapters and an in‑process YARP reverse proxy so new ASP.NET Core controllers roll out while old ones continue serving traffic; uses Upgrade Assistant to scaffold the Core project, shares business logic via a .NET Standard/multi‑targeted library, keeps EF6 where possible, replaces bundling with Web Optimizer, bridges session and auth with remote JSON endpoints, and partitions Hangfire queues; process succeeds in staged deployments with minor latency overhead and no big‑bang rewrite.
AI-written summary · about
chapters (13)
- 0:00.NET 8 migration challenges
- 2:16Migrate from .NET Framework to 8
- 9:17Legacy app dependencies
- 11:26Incremental migration with adapters
- 17:02Upgrade assistant demo
- 29:38Deploy empty ASP.NET Core app
- 32:07Shared business logic library
- 37:20First controller to migrate
- 40:51Static assets and bundling
- 47:56Session state handling
- 54:18Hangfire jobs management
- 58:15Auth strategies for dual apps
- 1:00:02Final decommission steps
related talks
01h 00mOld to Gold: How to Modernize Your Legacy ASP.NET Apps Gradually
01h 04mMigrate Your Legacy ASP.NET Projects to ASP.NET Core Incrementally with YARP
44mModernize your ASPNET based systems using the Strangler Fig pattern
46mWhat's New in ASP.NET Core 8 and Blazor 8
47mUnleashing Clean Architecture in .NET 8
01h 02mSolid ASP.NET Core
16mFull stack web in .NET 8 with Blazor
56mWriting simpler ASP.NET Core