This is the next in a series of blog posts that will cover the topics discussed in the ASP.NET Community Standup. The community standup is a short video-based discussion with some of the leaders of the ASP.NET development teams covering the accomplishments of the team on the new ASP.NET Core framework over the previous week. Join Scott Hanselman, Damian Edwards, Jon Galloway and an occasional guest or two discuss new features and ask for feedback on important decisions being made by the ASP.NET development teams.
Each week the standup is hosted live on Google Hangouts and the team publishes the recorded video of their discussion to YouTube for later reference. The guys answer your questions LIVE and unfiltered. This is your chance to ask about the why and what of ASP.NET! Join them each Tuesday on live.asp.net where the meeting’s schedule is posted and hosted.
ASP.NET Community Standup 12/14/2016
On December 12th, we announced updates to the .NET Core tooling for Visual Studio 2017 RC. This update came with enhancements and bug fixes to the earlier release of VS 2017 .NET Core tooling. Some areas addressed include:
csproj file simplification: .NET Core project files now use an even more simplified syntax, making them easier to read.
CLI commands added: New commands added for adding and removing project to project references.
Overall quality improved: Bug fixes in xproj to csproj migration, project to project references, NuGet, MSBuild and ASP.NET Core with Docker.
For more details on the .NET Core Tooling improvements please read the announcement here.
Questions and Answers
Question: With the new VS 2017 .NET Core tooling updates I get csproj file when I create a new application. Will I ever want to use project.json again?
— The logic is when you go into a new folder and type dotnet, it needs to find an SDK. It will by default use the latest version of the dotnet SDK available. However, by using global.json you can specify previous versions of the SDK you would like to use.
Question: Is global.json still the router for the dotnet SDK? checkout this post for reference
— In the current build it is but, will be replaced. The intent is we will still support side-by-side SDKs with the ability to switch between them.
See you at our next community standup!