At some point before attempting to build, you need to delete the obj folder. More than one person showed this to solve the problem.

https://developer Communities.udio.com/content/problem/312180/projects-fail-to-build-in-1580- due-to-errors-from.html”rel=“noreferer”>https://developer communities.udio.com/content/problem/312180/projects-fail-to-build-in-1580- due-to-erors- from.html>

虽然@Señor CMass回答过去帮助我,但I m现在发现(自安装以来)。 NET Core SDK v2.2 - 我不知道这段话是否相关,我也需要close和视力重新开放<。 因此,对我来说,reci是:

• Clean solution
• Delete obj folders
• Delete the .vs folder (optional, if you get red lines but it builds OK)
• Close and reopen Visual Studio
• Then build

Add this: <RuntimeIdentifier>win</RuntimeIdentifier> to your project file, for example after element TargetFrameworkVersion. Make sure the element name is singular. RuntimeIdentifiers on the other hand is used in the new csproj format

或者说,你可以把你作为管理人的威斯特尔语的文字放在你项目的基本目录上。

Get-ChildItem . -include bin,obj -Recurse | foreach { remove-item $_.fullname -Force -Recurse }

本稿将删除所有切片和双管。

在我解决问题的步骤之后,我在2019年5月16日(16.8.6)也发生了同样的错误。

1. Close visual studio (other visual studio instances may remain)
2. Delete all bin and obj folders in all projects in the solution
3. Reopen solution and Build

请注意,如果存在双管齐下,只删除双管束,你也需要删除双管。

采用一揽子方案的项目是否存在这一问题 人工恢复一揽子计划时的考虑

NuGet.exe restore my.sln

as part of a TeamCity build (so might be related nf313743 s answer https://stackoverflow.com/a/60951212/128384) and then building projects using msbuild. This would result in the following error when msbuild begins dealing with the PackageReference:

[ResolveNuGetPackageAssets] C:Program Files (x86)Microsoft Visual Studio2017CommunityMSBuildMicrosoftNuGet15.0Microsoft.NuGet.targets(186, 5):
Your project file doesn t list  win-x86  as a "RuntimeIdentifier". You should add  win-x86  to the "RuntimeIdentifiers" property in your project file and then re-run NuGet restore.

在这里删除 ob头等,因为它们通过<条形状> 插入<> > > > > ; 添加一个可操作性识别器,但在VS2017 指挥线上打上准确的同一条,因此,明显区别是City如何建立环境。

第1号呼吁的输出中可以找到主犯:

NuGet.exe restore my.sln -NonInteractive
MSBuild auto-detection: using msbuild version  16.10.2.30804 
from  C:Program Files (x86)Microsoft Visual Studio2019CommunityMSBuildCurrentin .

它使用从VS2019安装中铺设的ms,而该项目是由VS2017建造的,因此,有些地方在混杂了那些没有预料到的不相容。 不管怎么说,关键因素很可能是,团队会创造像VS2017指挥线这样的完全环境,NuGet文件指出

By default the MSBuild in your path is picked,
otherwise it defaults to the highest installed version of MSBuild.

因此,它使用了VS2019。 解决办法是人工通过<代码>-MsBuildPath至NuGet,并将之与组群中选定的建筑群对应。

NuGet.exe -msBuildPath "%MSBuildTools15.0_x86_Path%" restore my.sln

(and it turns out teamCity itself is also plagued by this in its own NuGet step: How to set the MSBuild verision for TeamCity NuGet Installer?)

我也存在同样的问题。 我的错误是:

error : Your project file doesn t list win10 as a "RuntimeIdentifier". You should add win10 to the "RuntimeIdentifiers" property in your project file and then re-run NuGet restore.

Well, it turned out I just had to change by build target from "Any CPU" to something else (x64 for example)...

我也有类似的情况。 我试图在安装视力演播室时通过调制成解决办法,仅仅安装了最新版本的“2017年”建筑工具。 我在此采取的步骤:

1. dotnet restore a.sln (There are some .Net Standard Library project in this solution, the others are .NET 4.7.2 projects).
2. call msbuild.exe to build this solution.
3. I got the error of "missing RuntimeIdentifier".

你们的项目档案没有打赢“RuntimeIdentifier”。 你们应当把“RuntimeIdentifiers”财产添加到你们的项目档案中,然后重新启用NuGet。

It seems an issue in the old version of Nuget. Please refer here. Finally, I resolved it via restore packages with the latest Nuget (v5.0.2). the steps:

1. Delete obj and bin folders
2. nuget.exe restore a.sln
3. call msbuild.exe

you got to figure out which projects in your solution trigger this error. you can find this if you look at the error panel. go to that projects locations and delete both the bin and the obj folders. then rebuild. should be alright

我有同样的问题,跨越羊毛建筑链(VS2017/VS2019)——这里是我确定的——通过<条码>清洗的武力。

Your project file doesn t list win as a "RuntimeIdentifier". You should add win to the "RuntimeIdentifiers" proper ty in your project file and then re-run NuGet restore

Remove Intermediary Build Output Artifacts

rimraf *obj**

“RuntimeIdentifier”应比此处描述的内容更像:https://learn.microsoft.com/en-us/dotnet/core/rid-catalog 。

对我来说,该秘密埋在:github : 我在同一个目录中拥有两卷立案卷,这显然是令人沮丧的。 逐一解决了这一问题。