+91 97031 81624 [email protected]

Microsoft’s .NET Core 3.0 team is done with the project to port the venerable .NET Framework API to the open source platform.

Program Manager Immo Landwerth made the announcement in the form of an issue on GitHub (where else?) and stated that the gang had reached the point where it reckoned that everything needed for “modern workloads” had been ported.

Which is to say not quite everything that currently lurks in the elderly .NET Framework.

The number of APIs ported to .NET Core 3.0 currently stands at over 120,000, just over half of all .NET Framework APIs (and up from the 18,000 that turned up in the original .NET Core 1). There are also another 62,000 APIs in .NET Core 3.0 that aren’t in the .NET Framework.

All in all, the team estimates that .NET Core 3.0 has approximately 80 per cent of the .NET Framework’s API surface, and that’s OK.

While Microsoft is keen that new .NET applications be written using .NET Core, the vast swathe of legacy apps built with .NET Framework can stay where they are, since version 4.8 will continue to see support. It simply won’t get all the new toys headed .NET Core’s way.

The same goes for Web Forms, WCF sever and Windows Workflow, which have no place in the bright .NET 5 future where .NET Core 3.0 is headed.

Microsoft says the .NET Framework API Porting Project finished

Expert discussing about this at reddit as in the above image

Which is to say not quite everything that currently lurks in the elderly .NET Framework.

The number of APIs ported to .NET Core 3.0 currently stands at over 120,000, just over half of all .NET Framework APIs (and up from the 18,000 that turned up in the original .NET Core 1). There are also another 62,000 APIs in .NET Core 3.0 that aren’t in the .NET Framework.

All in all, the team estimates that .NET Core 3.0 has approximately 80 per cent of the .NET Framework’s API surface, and that’s OK.

While Microsoft is keen that new .NET applications be written using .NET Core, the vast swathe of legacy apps built with .NET Framework can stay where they are, since version 4.8 will continue to see support. It simply won’t get all the new toys headed .NET Core’s way.

The same goes for Web Forms, WCF sever and Windows Workflow, which have no place in the bright .NET 5 future where .NET Core 3.0 is headed.

Read full article at The Register 

Microsoft says .NET Framework porting project is finished: If your API’s not on the list, it’s not getting in  

Real time Project Training in ASP .NET, MVC – Dot Net course Hyderabad

Coding is the new literacy: 5 programming languages to master for high paid Jobs

Get ASP Net, MVC Developer JOB support |Online Technical Support

Online Job Support from India | Asp.Net, MVC, Selenium Testing C#

Get Manual Testing Online Technical Support by Skilled Consultant

 

 

Pin It on Pinterest

Share This