.NET Core 3.0 API currently has a total of about .NET 80% Framework API, and the rest have not yet ported from .NET Framework to the .NET Core API, consider Microsoft released as open source.
Microsoft said through .NET Core 3.0, they now have all the modern technology required to easily migrate workload, whether desktop applications, mobile applications, console applications, websites or cloud services. To this end, they plan to no longer existing on the .NET Framework 3.0 Core technology into the .NET , and consider using open-source MIT license does not intend to migrate to .NET Core .NET Framework 3.0 code base.
Of course not transplant API does not mean that we do not have any chance in the use of new technologies, but these technologies do not appear in the .NET Framework code base.
Let us look at the development process of .NET Core and the .NET Framework.
Starting .NET Core 1.0, it is only a very small set of API, which contains only about 18,000 .NET Framework API. By the .NET Standard 2.0 , Microsoft is trying to share code between .NET Framework, .NET Core and Xamarin, therefore .NET Core 2.0 provides approximately 38,000 .NET Frameworks API. In addition, Microsoft has also built a compatibility kit bag - Windows Compatibility Pack , and the kit bag and let .NET Core increased by about 21,000 .NET Framework API. So far, around about 60,000 API ported to .NET Core.
In the latest release of .NET Core 3.0 , Microsoft added WPF and WinForm, the total number of the .NET Framework API ported to .NET Core is therefore more than 120,000, more than half of the total number of .NET Framework API.
There is also to be noted is that Microsoft deliberately emphasized that they add in .NET Core in about 62000 .NET Framework is not the API, so if only the total number of API comparison, the number of API .NET Core accounted for about .NET Framework 80% API's.
Microsoft said the future will be based on .NET .NET Core, at the Build 2019 conference, Microsoft announced AppDomains, Remoting, Web Forms, WCF server and Windows Workflow will not be ported to .NET Core. Currently the plan is no longer any .NET Framework technology ported to .NET Core. The previously mentioned Microsoft will open source do not intend to migrate to .NET Core .NET Framework 3.0 code base, hoping to create more OSS projects make a contribution to the community.
For example, there are already two of this community-based project was born - CoreWF and CoreWCF .