Tales from the NET 8 Migration Trenches
summary
Migrates active .NET Framework 4.8 apps to .NET 8 incrementally by standing up an ASP.NET Core front end that forwards unknown routes to the legacy app, using System Web Adapters and a self-hosted YARP proxy. Creates a multi-target shared library for business logic, replaces MVC bundling with WebOptimizer or a Node toolchain, implements session via adapter-backed API endpoints, and proves the phased cutover works in production with final deletion of legacy code.
AI-written summary · about
chapters (13)
- 0:00🚀 Introduction to the .NET 8 Migration Process
- 2:30Why Migrate? The Need for .NET 8 Migration
- 6:00Understanding the Challenges of Migrating from .NET Framework 4.8
- 10:00Setting Up the System Web Adapters for Incremental Migration
- 13:30Using YARP Proxy for Smooth Transition Between Frameworks
- 18:00Tracking the Size of the Application: Controllers, HTTP Endpoints, and Middleware
- 22:00Navigating the Migration of Complex Business Logic and Dependencies
- 26:00Migrating Controllers, Views, and Static Assets Incrementally
- 30:00Handling Session State Migration: ASP.NET Core vs. Full Framework
- 34:00Dealing with Dependency Injection and Legacy Logic
- 38:00Testing and Monitoring During the Migration Process
- 42:00Final Steps: Deleting Legacy Code and Completing the Migration
- 44:00Conclusion: Incremental Migration Success & Parting Thoughts
related talks
53mTales From the .NET 7 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
41mTaming .NET Framework legacy WebApi
33mMigrating .NET and .NET Core to Pivotal Cloud Foundry
14mModernize .NET Apps
01h 02mIs your code ready for .NET Core?