I searched this problem but none of the solutions worked. I have Visual Studio Professional 2015 installed and I am using TFS. My NuGet version is 3.1.6. This problem is happening only in my C# Web API/MVC project.
I am getting the below error:
This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ..\packages\Microsoft.Net.Compilers.1.0.0\build\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.
The issue for me was that NuGet couldn't automatically get/update the packages because the full file path would be too large. Fixed by moving my solution to a folder in my Documents instead of a deeply nested folder.
Then can right-click on solution and select "Restore NuGet Packages" (which probably isn't necessary if you just build it and let it do it for you), and then select "Manage NuGet Packages for Solution" to get all the packages updated to the latest version.
This was for a solution of a sample ASP MVC application downloaded from Microsoft's web site.
I solved my issue by removing this code from
.csproj
file:You can also use the suggested error message as a hint. Here's how, find the Manage Packages for Solution, and click on the resolve missing nuget package.
That's it
For DevOps/build engineers, you can probably fix this running
nuget restore
against the affected SLN, or project if you lack a SLN. I have to do this for our CI/CD builds for all our UWP projects.VS2015
call "%VS140COMNTOOLS%VsDevCmd.bat"
or
VS2017
call "%ProgramFiles(x86)%\Microsoft Visual Studio\2017\Enterprise\Common7\Tools\VsDevCmd.bat"
call nuget restore MyStuff.SLN
orcall nuget restore MyStuff.csproj
if there's no SLN.A combination of the 2 answers worked for me. First I modified the .csproj file to remove the reference to 1.0.0 version
and then did
from the and it worked.
I had this exact frustrating message. What finally worked for me was deleting all files and folders inside /packages and letting VS re-fetch everything the next build.