This article mainly introduces in detail the causes and solutions of compilation errors when creating .net standard class library in Visual Studio 2017. It has certain reference value. Interested friends can refer to it
Formal The version was released last month. From then on, I often receive update prompts. I guess there are still a lot of problems! Of course, the ones that attract me the most are .net standard and .net core.
#I just recently came into contact with the .net standard project. I created a new class library and compiled it directly, but an error occurred! ! I immediately felt bad and my interest in it was greatly reduced!
If you are a newbie, you will probably complain immediately! As a veteran, let’s calm down and take a look at the reason.
Look at the last item:
The asset file "c:\users\newblifes\documents\visual studio 2017\Projects\TestDemo\TestDemo\obj\project.assets cannot be found" .json". Run a NuGet package restore to generate this file. E:\ProgramData\VS2017\MSBuild\Sdks\Microsoft.NET.Sdk\build\Microsoft.NET.Sdk.targets 92
This should be because the .net standard package has not been restored, causing the connection The error cannot be found in the System namespace.
There is no NETStandard.Library under the dependencies, but there is no problem with the project file settings:
The first reaction is to install the NETStandard.Library package as .net standard It is impossible for the class library to not have this package, but why can't it automatically restore the package?
Since this is a newly installed Visual Studio 2017 without much settings, I suddenly thought about whether there is a problem with the settings of Visual Studio package management?
Opening the tab is really not checked! ! It turns out that the default settings have changed, and Visual Studio 2015 has it checked by default! !
Set as follows according to your preference:
Compile the project again:
#The desired result has appeared, and this time I can do things with peace of mind.
Summary
Friends who have newly installed Visual studio 2017, remember to take a good look at the settings tab before using it, and add relevant settings, otherwise something may go wrong. I wasted a lot of time and still couldn’t figure it out!
The above is the detailed content of Solve the problem of compilation error when creating .net standard class library in Visual Studio 2017. For more information, please follow other related articles on the PHP Chinese website!