Still on 4.8 or lower? A Practical Guide to Moving Your "Un-Migratable" .NET Apps
What this session covers
Let’s be honest: if your .NET Framework app was easy to migrate, you would have done it three years ago. You’re likely stuck with legacy WCF services, deep dependencies on System.Web, or a NuGet graph that looks like a bowl of yarn. The .NET Upgrade Assistant is a great start, but it’s the last 20% of the migration—the part that the tools can’t automate—that actually keeps us up at night.
In this session, we’re moving past the “hello world” migration demos. We’ll look at real strategies for modernizing .NET Framework 4.x apps into .NET 8/9/10 without a complete rewrite.
We will get into the weeds on:
The “Bridge” Strategy: Using YARP (Yet Another Reverse Proxy) to migrate your app piece-by-piece rather than a “Big Bang” release.
The Dependency Trap: What to do when your critical library hasn’t been updated since 2014.
Modernizing the “Un-modernizable”: Strategies for dealing with legacy config systems and static state that modern .NET hates.
This isn’t a theoretical talk about “embracing innovation.” It’s a tactical session for developers who need to get their legacy code onto a supported, performant, and AI-ready platform without breaking the business.
World Congress 2026 North America
Related talks
- How to generate business value through performance optimizations
Nikolai Sidiropulo · Meta
Thu 24 Sep · Stage 4
- Offloading IoT State: Solving the Memory Crisis on Legacy Hardware
Pravin Nagare · Roku
Fri 25 Sep · Outdoor Stage
- Beyond Vibe Coding: An AI Builder’s Guide to Migrating 10k+ React Components
Shubham Chaurasia · Meta
Fri 25 Sep · Stage 7
- The AI Dependency Challenge: Your AI coding assistant is making dependency decisions. Who’s checking

Meredith Eisen & Vince Hinojosa
Fri 25 Sep · Stage 10