.NET Platform Overview and Roadmap Options

codeling Posts: 1153 Points: 4845
Posted: Monday, November 18, 2019 10:24:41 AM

Migrating from .NET Framework to .NET Core 3.0

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'

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


Several APIs that are not supported in the out-of-the-box version of .NET Core may be available from the Microsoft.Windows.Compatibility nuget package. 

codeling Posts: 1153 Points: 4845
Posted: Monday, November 18, 2019 10:29:10 AM
Users browsing this topic