Shulou(Shulou.com)06/01 Report--

Net Core how to build configuration files from project.json to .csproj, this article describes in detail the corresponding analysis and solutions, hoping to help more partners who want to solve this problem to find a more simple and easy way.

Starting with .NET Core SDK 1.0 Preview 3 build 004056, .NET Core deprecated project.json and returned to .csproj, mainly for compatibility with MSBuild, as detailed in Announcing .NET Core Tools MSBuild "alpha".

If you install .NET Command Line Tools (1.0.0-preview3-004056), running dotnet new will not create a project.json file, but instead a .csproj file with the following contents:

Exenetcoreapp1.0 1.0.1 1.0.0-alpha-20161104-2 All

Dotnet restore, dotnet build, dotnet publish, and dotnet run all use this .csproj file, and project.json is no longer supported.

The .NET Core project created with Visual Studio for Mac also has .csproj and no project.json.

The .NET Core project created with Visual Studio 2017 RC also has .csproj and no project.json.

There are two ways to convert project.json to .csproj:

1) in the project folder where project.json is located, run the dotnet migrate command.

2) Open the existing .sln with Visual Studio 2017 RC, and VS2017 will automatically convert it for you (it is found that the automatic conversion of VS2017 is not reliable, or the dotnet migrate command is reliable).

.csproj of .NET Core is not currently supported in Visual Studio 2015.

This is the answer to the question about how .NET Core builds configuration files from project.json to .csproj. I hope the above content can be of some help to you. If you still have a lot of doubts to solve, you can follow the industry information channel for more related knowledge.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.