Earlier this week, Microsoft published the roadmap for .NET Core 2.1, ASP.NET Core 2.1 and EF Core 2.1, expected to be out in the first quarter of 2018. The team also talked about several new features with this new release. This release is more of a feedback-oriented release based on .NET Core 2.0 release. The.NET Core 2.0 is a huge success and already more than half a million developers are now using .NET Core 2.0. All thanks to .NET Standard 2.0 release . In this post find out about the new features of .NET Core 2.1. 

This post will be comparing the performance of RyuJIT in .NET Framework 4.6.2 to its performance in .NET Core 2.0 and .NET Framework 4.7.1.  

• Preventing .NET Garbage Collections with the TryStartNoGCRegion API  
• Stopping Garbage Collection in .NET Core 3.0 (part II)
• Stopping Garbage Collection in .NET Core 3.0 (part I)  

.NET 5 Preview 7 is now available and is ready for evaluation. Here’s what’s new in this release:

• Blazor WebAssembly apps now target .NET 5
• Updated debugging requirements for Blazor WebAssembly
• Blazor accessibility improvements
• Blazor performance improvements
• Certificate authentication performance improvements
• Sending HTTP/2 PING frames
• Support for additional endpoints types in the Kestrel sockets transport
• Custom header decoding in Kestrel
• Other minor improvements 

In this post, I will describe how to port a desktop application from .NET Framework to .NET Core. I picked a WinForms application as an example. Steps for WPF application are similar and I’ll describe what needs to be done different for WPF as we go. I will also show how you can keep using the WinForms designer in Visual Studio even though it is under development and is not yet available for .NET Core projects. 

Explore These Free UI Control Libraries for .NET MAUI 

Support for the .NET 6 SDK, including Hot Reload  

NET 6 Gets Blazor WebView Controls for WPF, WinForms 

Move Over, Stack Overflow: Microsoft Launches Q&A for .NET