I have a solution/team project set up in visual studio 2013 and for some time have had a working NuGet Microsoft.Bcl Async Package installed for NET Framework 4.0. Today whe
A possible solution: If you are seeing yellow triangles over most of your System references, edit your .csproj
file (back it up just in case), scroll to the bottom of the file, and delete these lines...
This project references NuGet package(s) that are missing on this computer. Enable NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}.
Like many others, I've been using a centralized .packages
folder outside of source control. This is done by having the following lines in your NuGet.Config
file:
One of the steps in achieving this, is to check your project file does not use the old NuGet.targets
file anymore (the only file in your .nuget
solution folder should be NuGet.Config
).
When NuGet thinks it should check the NuGet.targets
file, and it's not there, it will fail checks to basic references too (like System.Core
, WindowsBase
and PresentationCore
).
Update: See this related topic/answer on how to completely do away with .nuget
folders in your solution! It can be set at user-profile level in your AppData.