The Microsoft .NET Core 3.0 team has finished with the project to port the venerable .NET Framework API to the open source platform.
The Immo Landwerth program administrator made the announcement in the form of a problem on GitHub (where else?) And declared that the gang had reached the point where he considered everything necessary for "modern workloads" He had been ported.
From now on, we don't plan to port any more .NET Framework APIs to .NET Core. https://t.co/5EChTGgUbn
– Immo Landwerth (@terrajobst) October 14, 2019
That is, not everything currently lurking in the .NET Framework.
The number of APIs ported to .NET Core 3.0 is currently more than 120,000, just over half of all .NET Framework APIs (and more than 18,000 that appeared in the original .NET Core 1). There are also another 62,000 APIs in the .NET Core 3.0 that are not in the .NET Framework.
All in all, the team estimates that .NET Core 3.0 has approximately 80 percent of the .NET Framework API area, and is fine.
While Microsoft is interested in having new .NET applications written using .NET Core, the large number of legacy applications created with the .NET Framework can remain where they are, as version 4.8 will continue to receive support. You simply will not get all new toys to go to .NET Core.
The same goes for Web Forms, WCF sever and Windows Workflow, which have no place in the bright future of .NET 5 where .NET Core 3.0 is being directed
Microsoft's hope is for the OSS community to pick up the technology orphaned at the end of the porting project, in the same way that projects have emerged to port the Windows Workflow Foundation runtime and the Windows Communication Framework to .NET Core 3.0 in the form of CoreWF and CoreWCF.
To that end, the Windows giant is investigating the release of more of that .NET Framework code under the MIT license for developers to analyze carefully. Presumably, once all oaths and sarcasm have been removed from the comments.
However, for those who need that API to behave, there is a ray of hope. Landwerth sang: "In the future, we are focusing our resources on the incorporation of new technologies," but in response to the inevitable plea for just one more method, he replied: "I see minor convenience APIs like
CompileToMethod still as a fair game, because it can be considered as an evolution of .NET Core. "
He continued to clarify that the fact that an API exists in the .NET Framework does not necessarily mean that it cannot be considered to add it. NET Core, but equally now there must be more motivation than simply being on the legacy platform.
And with a flourishing, all problems labeled "port to core" were closed. ®
Your guide to being truly data driven with unmatched data analysis performance