How to Modernize Your Legacy ASP.NET Apps Gradually
summary
Live migration demo upgrades an ASP.NET MVC app side‑by‑side to ASP.NET Core using YARP as a reverse proxy and the net Upgrade Assistant for project conversion; a utilities class becomes netstandard2.0, one controller and view move into the new app, and CSS/JS bundling breaks so WebOptimizer/LigerShark is added to rebuild bundles. The page ends up half migrated (HTML proxied from legacy, static assets served by Core) and works in the demo; system.web adapters handle session/auth bridging for full migration.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 5:00Legacy vs modern .NET
- 10:00Strangler fig migration
- 12:47Reverse proxies role
- 15:56YARP explained
- 23:23YARP migration scenarios
- 26:34Upgrade Assistant overview
- 28:16Live demo setup
- 33:14Class library to .NET Standard
- 39:16Web app to ASP.NET Core
- 45:38Testing migrated app
- 50:17CSS and bundling fixes
- 57:45System.Web Adapters
- 1:00:11Summary & Q&A
related talks
32mModern JavaScript, without giving up on Rails Jonathan Johnson
34mSurviving the Big Rewrite
31mSo Long, Hoboken: Migrating a Huge Production Codebase from Sinatra to Rails
58mASP.NET Core meets OWASP Top 10 2025
23mCrafting Rails Culture
38mOur Fight Against Super Bad Patterns in Legacy Rails Apps
36mWorking Compassionately with Legacy Code
39mThe Long Ball - Upgrading long lived Rails apps from 1.x-4.0
