1. Best practices for API versioning
2. How are REST APIs versioned
   
3. Routing constraint sample
4. Versioning RESTful Services
   
5. Best Practices for Designing a Pragmatic RESTful API
   
6. API versioning
7. ASP.NET Web API Versioning with Media Types

• Class Library (.NET Framework)
• Class Library (.NET Standard)
• Class Library (.NET Core) 

[CLI] Build-time performance improvements.
[CLI] Global tools; replaces .NET CLI Tools (DotNetCliToolReference).
[CoreCLR] Minor-version roll-forward.
[CoreCLR] No-copy array slicing with Span<T>.
[CoreFX] HttpClient performance improvements.
[CoreFX] Windows Compatibility Pack.
[ASP.NET] SignalR is available for .NET Core.
[ASP.NET] HTTPS is on by default for ASP.NET.
[EF] Basic lazy loading support.
[EF] Support for Azure Cosmos DB.

At work, we are planning to migrate our WPF application from .NET Framework 4.7 to .NET Core 3.0. The main reason for doing so is that it was always a big pain to organize the updates of the .NET Framework on our customer machines. So being able to bundle .NET Core with our application is a big plus for us. Then, for sure, we are looking for the performance improvements brought by .NET Core and finally the new capabilities brought by the fast pace of innovation of .NET Core. 

Performance improvements in ASP.NET Core 6 

.NET Core performance revolution in Rider 2020.1 

Performance Improvements in .NET Core 3.0 

Performance is a Key .NET Core Feature