Today we are releasing updates to the .NET Core SDK and Visual Studio 2017 RC. Important areas will be highlighted below and you can find additional details on the .NET Blog and the Visual Studio Blog.
We’re getting close to the final release of .NET Core Tools and Visual Studio 2017 making it a great time to try out the migration tools on your projects. and give us feedback on the experience. If you want to try .NET Core Tools in Visual Studio 2017, visit Visual Studio 2017 RC to download. You’ll need to choose the Web workload when installing.
If you’re using another dev tool on Windows, macOS or Linux, go to the .NET Core RC Download for all installation options.
Want a helping hand from Microsoft for migrating your .NET Core and ASP.NET Core projects from project.json to the new VS2017 csproj format? Please click here.
A great deal of work has gone into dotnet new since our last update continuing to improve this important tool. An important thing to know is the default behavior of dotnet new no longer defaults to a creating a console template. Details and a walk through can be seen in the .NET Blog.
Important changes have been made to our tags for this release in the dotnet repo. The latest and nanoserver tags now utilize the msbuild SDK and are not compatible with project.json projects. Additional details can be seen in the .NET Blog.
Fedora 23 and openSUSE 13.2 recently went out of support, per their respective project lifecycle. As a result, we are now no longer supporting or building for Fedora 23 and openSUSE 13.2.
We will be publishing a more formal policy on Linux distro support, in particular on managing end-of-life of distros. There will be opportunity for feedback on the policy before it is finalized.