我研究了这个问题，但没有一个解决办法有效。我安装了Visual Studio Professional 2015，我正在使用TFS。我的NuGet版本是3.1.6。这个问题只发生在我的c# Web API/MVC项目中。
我得到以下错误:
这个项目引用了NuGet包(s)，这是缺失的
电脑。使用NuGet包还原来下载它们。更多的
信息，见http://go.microsoft.com/fwlink/?LinkID=322105。的
丢失的文件是
. . \ \ Microsoft.Net.Compilers.1.0.0 \制造\ Microsoft.Net.Compilers.props包
I do not have .nuget folder in my solutions.
I have a packages folder in the solution and when I delete it, it seems like NuGet does rebuild the dependencies but the project still has the above error.
I tried removing the project from TFS and it didn't fix it.
Along with the above error, all the references in the project have yellow warning signs and say they are missing.
When I checked the NuGet Package Manager for the project, everything that is "missing" has a green tick next to it, including Microsoft.Net.Compilers.
I tried adding a new Web API/MVC project and it faced a similar problem where most references such as Owin were "missing" with the yellow warning sign.
对于DevOps/构建工程师，您可能可以针对受影响的SLN或缺乏SLN的项目修复此运行nuget恢复。我必须为我们所有UWP项目的CI/CD构建这样做。
Make sure nuget is installed on the build slave either in Visual Studio or standalone. If it's the latter, make sure it's in PATH and skip step 2.
Either open the VS Dev CMD console, or load it via an already open one, which you can do with the instructions below:
VS2015 call "%VS140COMNTOOLS%VsDevCmd.bat"
or
VS2017 call "%ProgramFiles(x86)%\Microsoft Visual Studio\2017\Enterprise\Common7\Tools\VsDevCmd.bat"
call nuget restore MyStuff.SLN or call nuget restore MyStuff.csproj if there's no SLN.
对于在这里遇到我遇到的问题(在构建服务器上恢复了一些包，但不是所有包)的任何人来说，对我来说，难题的最后一块是添加NuGet。config在我的解决方案的根文件中，是. sln文件的兄弟，正如David Ebbo在这里解释的:http://blog.davidebbo.com/2014/01/the-right-way-to-restore-nuget-packages.html。
从Ebbo的博客文章来看，文件内容对我来说很简单
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<add key="nuget.org" value="https://www.nuget.org/api/v2/" />
</packageSources>
</configuration>
更新:
v3的NuGet API URL已更改(截至2016年9月)。从https://www.nuget.org/
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
为了在这里展开一些答案，是的，你可以从你的.csproj文件中删除以下块:
<目标
这解决了问题，但在我的情况下，我注意到我有额外的引用。net。编译器和。codedom。不同版本的供应商:
<Error Condition="!Exists('..\packages\Microsoft.Net.Compilers.1.0.0
<Error Condition="!Exists('..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.0\
<Error Condition="!Exists('..\packages\Microsoft.Net.Compilers.2.0.1
<Error Condition="!Exists('..\packages\Microsoft.CodeDom.Providers.DotNetCompilerPlatform.1.0.3\
当我的包裹。配置仅参考以下内容:
<package id="Microsoft.Net.Compilers" version="2.0.1"
<package id="Microsoft.CodeDom.Providers.DotNetCompilerPlatform" version="1.0.3"
从.csproj文件中删除1.0.0项解决了这个问题。
