1

When migrating packages from VS2013 to VS2015, all external and internal references for Data Access Layer Project were completely broken. References and packages for all other projects are fine. When uninstalling and re-installing/re-adding the references they still appear as broken.

Has anyone ever encountered this before? If so, what did you do to fix this?

w.brian
  • 16,296
  • 14
  • 69
  • 118
e.botha
  • 51
  • 7
  • I've had this before when one or more projects were on different .NET versions. Check each project's properties and ensure they're targetting the correct framework version. – heymega Sep 03 '15 at 13:50
  • Also, check to see if there are updates in the packages, downloaded from the NuGet gallery. Right-click on References -> Manage NuGet Packages, and when the dialog appears choose Updates. Beware, however, you may need the same package version, so consider replacing current with a newer one only if current has not been compiled for the .NET version you use. – Alexander Christov Sep 03 '15 at 13:57

2 Answers2

0

I ended up removing the project from Team Foundation Server, opened it up with Visual Studio 2013 and mapped it to a different location. The program then rebuilt successfully and now when opening it with Visual Studio 2015 all references are building.

e.botha
  • 51
  • 7
0

Have had the same issue. After analyzing project warnings I found that NuGet can't restore packages from solution's .nuget folder. In my situation enabling automatic package restore according to this answer fixed all errors.

Community
  • 1
  • 1
Volodymyr
  • 508
  • 1
  • 8
  • 16