Discussions on the Future of .NET Core 

What Was New for .NET Developers in 2018 & the Road Ahead  

Using the .NET Core 3.0 Preview with WPF 

deget/ddown; a downloader cli/api for dotnet 

.NET Core 2.2.1 release carries both security and non-security fixes. 

Question: What are differences between .Net Framwork, .Net Standard and .Net Core?

Answer:  

A common question from customers is how to have an RPC (as in .NET Remoting and Windows Communication Foundation) experience on .NET Core. We are contributing to the gRPC (grpc.io) project to ensure gRPC will have first-class support for .NET developers. 

Rider 2018.3.1 comes with fixes for:

Several issues in the debugger: RIDER-23087, RIDER-22932, RIDER-22770, RIDER-22887, and RIDER-22873.
Broken NuGet window after searching for “mongo” text (RIDER-22927).
Endless “Retrieving properties…” progress bar for Project Properties (RIDER-22924).
Inability to activate the dotTrace plugin via the License Server (RIDER-22876).
The “Failed to get the list of simulators” error on getting a list of iOS simulators (RIDER-22878).
The issue where a .jar setting file couldn’t be imported to Rider 2018.3 (RIDER-22823).
The misplaced position of inline parameter name hints (RIDER-22452).
 

We received tons of updates from Microsoft all across the board - from new experimental frameworks (Blazor) to quick iterations of the “Core Suite” (.NET, EF, and ASP.NET) and Visual Studio.