Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Start here: Choose your migration path
Your ASP.NET Framework application can successfully move to ASP.NET Core. The key is choosing the right approach for your specific situation.
Quick decision guide
For most production applications: Use the incremental migration approach - it's safer, faster to start, and keeps your app running in production throughout the process.
For smaller applications or greenfield rewrites: Consider the complete migration approach using our specialized guides.
The incremental approach: Best for most teams
Most non-trivial ASP.NET Framework applications should use incremental migration. This approach:
- Keeps your current app running while you migrate piece by piece
- Reduces risk by moving functionality gradually
- Delivers value faster with immediate deployment of migrated components
- Uses proven tools like YARP proxy and System.Web adapters
→ Start your incremental migration
Migration tools and resources
Automated assistance
- .NET Upgrade Assistant - Command-line tool for initial project conversion
- Visual Studio Extension - GUI-based upgrade assistance
Comprehensive guides
- Porting ASP.NET Apps eBook - Complete reference guide
- eShop Migration Example - Real-world case study
Changes to technology areas
Before you begin, review the technical differences between ASP.NET Framework and ASP.NET Core to understand key changes that may affect your migration.
Collaborate with us on GitHub
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
ASP.NET Core