Porting .NET Framework APIs to .NET Core has resulted in a lot of good work by the .NET team, but it’s reached the point where they’re unable to go much further.

The three-year .NET Core project started out with about 18,000 .NET Framework APIs in v1.0, with subsequent releases bringing that total to more than 120,000, which represent more than half of the ...

The beta of Windows Compatibility Pack adds 20,000 APIs to .Net Core for Windows, Linux, and MacOS web app developers, making it more like the Windows-only .Net Framework ...

Rustup 1.20, .NET Core 3.0 concludes the .NET Framework API porting project, The results of Angular and NativeScript’s first online hackathon are here Toggle navigation Subscribe ...

Having just shipped .NET Core 3.1, Microsoft is turning its focus to the next stop on its .NET roadmap.. Due in November 2020, .NET 5 (no "Core" and no "Framework") will mark the transition from ...

The plugin framework is a NuGet package that allows you to customise and extend a .NET application at runtime. Code examples are provided for ASP.NET Core, Blazor, Console Apps and WPF & WinForms ...

Code that calls Java APIs can convert to comparable C# code that uses the .Net Framework. The JLCA converts 90% of JDK-level 1.1.4 calls and emits issues in code for the other 10%.

The latest release of .NET 8 Preview 4 brings significant improvements to ASP.NET ... the future roadmap includes expanding metrics support to encompass additional APIs within the .NET framework.

I see minor convenience APIs like CompileToMethod still as fair game, because they can be thought of as an evolution of .NET Core. So it's really more about the motivation: we wouldn't add this API ...