Tales From the .NET 7 Migration Trenches
summary
A migration of a .NET 4.8 MVC app to .NET 7 happens incrementally: create an empty host that proxies into the old app, then move controllers one file at a time until the old app has no pages. Uses System.Web.Adapters plus a self‑hosted YARP reverse proxy, Upgrade Assistant for scaffolding, WebOptimizer for bundles, and multi‑targeted shared libraries so EF6 and business logic run on both runtimes. Sample inventory: 6 controllers, 58 actions (account controller has 22); delete migrated controllers to surface errors early.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:12Why migrate from .NET Framework
- 2:34Incremental migration strategy
- 5:22Cataloging the application
- 7:28Inventory of controllers
- 9:36Analyzing middleware
- 11:43Legacy components review
- 14:31Dependency migration paths
- 16:16System.Web Adapters setup
- 19:52Demo of migration tool
- 23:00Running the proxy in production
- 28:24Preparing shared libraries
- 31:55Migrating first controller
- 33:00Manual migration challenges
- 35:50Unsupported ASP.NET features
- 36:56Dependency injection changes
- 39:01Bundling and minification
- 41:51Dual bundling pipelines
- 43:16Controller migration process
- 44:40Session state handling
- 48:30Authentication migration
- 50:37Final cleanup steps
- 51:20Key migration takeaways
related talks
46mTales from the NET 8 Migration Trenches
58mUpgrade any .NET applications with the latest .NET stack.
57mMigrate your Web Apps to ASP.NET Core, one page at a time
01h 00mWhat's new and coming soon for .NET
14mModernize .NET Apps
46mWhat do I do with my old .NET Framework Apps?
01h 11mASP.NET Basics for Experts
55mModernizing your apps with .NET MAUI