There are fixes available for a number of blocking issues and adds support for push and list for compliant V3 servers. We also added support for the command line client to interact with v3 servers as well as project.json managed projects.

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. 

CoreWCF 1.0 has been Released, WCF for .NET Core and .NET 5+ 

Add command 'listRemoteDockerProcess' and variable 'pickRemoteDockerProcess' (#4607, PR: #4617)
Ensure we only start one instance of OmniSharp server (PR: #4612)
Update OmniSharp version to 1.37.11
  Include timing info in logged responses (PR: omnisharp-roslyn#2173)
  Defend against null value in BuildErrorEventArgs (omnisharp-roslyn#2171, PR: omnisharp-roslyn#2172)
  Updated to all the latest .NET SDKs (PR: omnisharp-roslyn#2166)
  Add support for GoToDefinition on source-generated files (PR: omnisharp-roslyn#2170)
  Add V2 version of GotoDefinitionService (PR: omnisharp-roslyn#2168)
  avoid NRE when document is null (PR: omnisharp-roslyn#2163))

 

Today, the Entity Framework Core team announces the first release candidate (RC1) of EF Core 5.0. This is a feature complete release candidate of EF Core 5.0 and ships with a "go live" license. You are supported using it in production.  

ASP.NET Core apps with native AOT have a smaller footprint, lightning-fast startup, and use less memory. 

In this blog post I’m going to talk about our .NET 8.0 GC feature called DATAS (Dynamic Adaptation To Application Sizes).