Of course, not porting API doesn't mean we don't have any chance of using new technologies, it's just that they don't appear in the. Net Framework code base.
Let's take a look at the development of. Net core and. Net framework.
Starting with. Net core 1.0, it has only a very small set of APIs, including only about 18000. Net framework APIs. adopt. net standard 2.0Microsoft is trying to share code between. Net framework,. Net core and xamarin, so. Net core 2.0 provides about 38000. Net frameworks APIs. In addition, Microsoft has built a compatibility package——Windows compatibility pack, which adds about 21000. Net framework APIs to. Net core. So far, around 60000 APIs have been migrated to. Net core.
up-to-date. net core 3.0Microsoft added WPF and WinForm, so the total number of. Net Framework API ported to. Net Core is more than 120000, more than half of the total number of. Net Framework API.
It should also be noted that Microsoft specially emphasizes that they have added about 62000 APIs that are not available in the. Net framework in the. Net core. Therefore, if you only compare the total number of APIs, the number of APIs in the. Net core accounts for about 80% of the. Net framework APIs.
Microsoft said the future of. Net will be based on. Net core. At the build 2019 conference, Microsoft announced that AppDomains, remoting, web forms, WCF server and windows workflow will not be migrated to. Net core. It is no longer planned to migrate any. Net framework technology to. Net core. As mentioned earlier, Microsoft will open source and does not intend to migrate to the. Net framework code base of. Net core 3.0, hoping to make a contribution to creating more OSS projects for the community.