Chapter 3. Migration to .NET Core 3.1

This chapter provides migration information for .NET Core 3.1.

3.1. Migration from previous versions of .NET Core

See the following Microsoft articles to migrate from previous versions of .NET Core to newer versions of .NET Core:

3.2. Migration from .NET Framework to .NET Core 3.1

Review the following information to migrate from the .NET Framework.

3.2.1. Migration considerations

Several technologies and APIs present in the .NET Framework are not available in .NET Core. If your application or library requires these APIs, consider finding alternatives or continue using the .NET Framework. .NET Core does not support the following technologies and APIs:

  • Windows Communication Foundation (WCF) servers (WCF clients are supported)
  • .NET remoting

Additionally, a number of .NET APIs can only be used in Microsoft Windows environments. The following list shows a few examples of these Windows-specific APIs:

  • Microsoft.Win32.Registry
  • System.AppDomains
  • System.Security.Principal.Windows

Consider using the .NET Portability Analyzer to identify API gaps and potential replacements. For example, enter the following command to find out how much of the API used by your .NET Framework 4.6 application is supported by .NET Core 2.1:

$ dotnet /path/to/ApiPort.dll analyze -f . -r html --target '.NET Framework,Version=4.6' --target '.NET Core,Version=2.1'

Several APIs that are not supported in the default version of .NET Core may be available from the Microsoft.Windows.Compatibility NuGet package. Be careful when using this NuGet package. Some of the APIs provided (such as Microsoft.Win32.Registry) only work on Windows, making your application incompatible with Red Hat Enterprise Linux.

3.2.2. .NET Framework migration articles

Refer to the following Microsoft articles when migrating from .NET Framework.