Overview of the porting process from .NET Framework to .NET Core
You might have code that currently runs on the .NET Framework that you're interested in porting to .NET Core. This article provides:
- An overview of the porting process.
- A list of the tools you may find helpful when you're porting your code to .NET Core.
Overview of the porting process
We recommend you to use the following process when porting your project to .NET Core:
Retarget all projects you wish to port to target the .NET Framework 4.7.2 or higher.
This step ensures that you can use API alternatives for .NET Framework-specific targets when .NET Core doesn't support a particular API.
Use the .NET Portability Analyzer to analyze your assemblies and see if they're portable to .NET Core.
The API Portability Analyzer tool analyzes your compiled assemblies and generates a report. This report shows a high-level portability summary and a breakdown of each API you're using that isn't available on NET Core.
This tool is similar to the portability analyzer, but instead of analyzing if things can build on .NET Core, it will analyze if you're using an API in a way that will throw the PlatformNotSupportedException at runtime. Although this isn't common if you're moving from .NET Framework 4.7.2 or higher, it's good to check.
This step involves converting your dependencies from the legacy
packages.configdoesn't work on .NET Core, so this conversion is required if you have package dependencies.
Create new projects for .NET Core and copy over source files, or attempt to convert your existing project file with a tool.
.NET Core uses a simplified (and different) project file format than .NET Framework. You'll need to convert your project files into this format to continue.
Port your test code.
Because porting to .NET Core is such a significant change to your codebase, it's highly recommended to get your tests ported, so that you can run tests as you port your code over. MSTest, xUnit, and NUnit all work on .NET Core.
Additionally, you can attempt to port smaller solutions or individual projects to the .NET Core project file format with the dotnet try-convert tool in one operation.
dotnet try-convert is not guaranteed to work for all your projects, and it may cause subtle changes in behavior that you may find that you depended on. It should be used as a starting point that automates the basic things that can be automated. It isn't a guaranteed solution to migrating a project.