Red Hat SummitChapter 6. Migration from previous versions of .NET
Upgrade your existing applications to .NET 10.0 to benefit from the latest performance improvements and long-term support. You can migrate from earlier .NET versions or port code from the .NET Framework to modernize your workloads.
6.1. Migration guidance for .NET
Microsoft provides detailed guidance for migrating between different versions of .NET and ASP.NET Core. If you are upgrading from an older .NET version, refer to the official Microsoft documentation for your specific upgrade path.
- Migrate from ASP.NET Core 9.0 to 10.0
- Migrate from ASP.NET Core 8.0 to 9.0
- Migrate from ASP.NET Core 7.0 to 8.0
- Migrate from ASP.NET Core 6.0 to 7.0
- Migrate from ASP.NET Core 5.0 to 6.0
- Migrate from ASP.NET Core 3.1 to 5.0
- Migrate from ASP.NET Core 3.0 to 3.1
- Migrate from ASP.NET Core 2.2 to 3.0
- Migrate from ASP.NET Core 2.1 to 2.2
- Migrate from .NET Core 2.0 to 2.1
- Migrate from ASP.NET to ASP.NET Core
- Migrating .NET Core projects from project.json
- Migrate from project.json to .csproj format
If you are migrating from .NET Core 1.x to 2.0, the initial sections of the Migrate from ASP.NET Core 1.x to 2.0 article provide the relevant guidance.
6.2. Porting from .NET Framework
When migrating an application from .NET Framework, refer to the official Microsoft documentation:
- General guidelines: Porting to .NET Core from .NET Framework
- Porting libraries: Porting to .NET Core - Libraries
- Migrating to ASP.NET Core: Migrating to ASP.NET Core
Some technologies and APIs from .NET Framework are not available in .NET Core or .NET. If your application or library depends on these APIs, you must either find an alternative or remain on .NET Framework.
.NET Core and .NET do not support the following technologies:
- Desktop applications, such as Windows Forms and Windows Presentation Foundation (WPF)
- Windows Communication Foundation (WCF) servers (WCF clients are supported)
- .NET remoting
Additionally, some .NET APIs are specific to Microsoft Windows environments and are not cross-platform. Examples of these Windows-specific APIs include:
-
Microsoft.Win32.Registry -
System.AppDomains -
System.Security.Principal.Windows
Some APIs that are not supported by default in .NET are available in the Microsoft.Windows.Compatibility NuGet package.
Use this package with caution. Many of the APIs it provides, such as Microsoft.Win32.Registry, only work on Windows. Using these APIs makes your application incompatible with Red Hat Enterprise Linux.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}