We started in .NET Core 1.0 with a very minimal API set that only included ~ 18 K of the .NET Framework APIs. With. NET Standard 2.0, we tried to make it much more viable to share code between .NET Framework, .NET Core, and Xamarin which resulted in approximately 38 K .NET Frameworks APIs being available in .NET Core 2.0. We also built theWindows Compatibility Packwhich made another 21 K .NET Framework APIs available to .NET Core, resulting in almost 60 K additional APIs. And in .NET Core 3.0 we added WPF and WinForms, which increased the number of .NET Framework APIs ported to .NET Core to over 120 k, which is more than half of all .NET Framework APIs.
It’s also worth pointing out that we added about 62 K APIs to .NET Core that don’t exist in .NET Framework. If we compare their total number of APIs, .NET Core has about 80% of the API surface of .NET Framework.
We announced that thefuture of .NETwill be based on .NET Core. And at Build 2019,Scott Hunter statedthat AppDomains, remoting, Web Forms, WCF server, and Windows Workflow won’t be ported to .NET Core.
With .NET Core 3.0, we’re at the point where we’ve ported all technologies that are required for modern workloads, be that desktop apps, mobile apps, console apps, web sites, or cloud services. That’s not to say that we don’t have any gaps or opportunities for new technologies, but we generally believe we won’t be finding them in the .NET Framework code base anymore. Moving forward, we’re focusing our resources on incorporating new technologies.
Simultaneously, we’re looking into releasing more of the.Net Framework code base under the MIT licenseon GitHub to allow the community to create OSS projects for technologies we’re not intending to bring to .NET Core. For example, there are already community projects forCoreWFand CoreWCF.
We’d like to thank everyone who filed issues with requests for APIs being ported. Those issues allowed us to prioritize and close the gaps that prevented people from porting to .NET Core.
But since we generally no longer plan to bring existing technologies from .NET Framework to .NET Core we’ll be closing all issues that arelabeled with port-to-core.
Discussion
To discuss this issue, please comment on the corresponding issue atdotnet / corefx # 41769.
GIPHY App Key not set. Please check settings