10

When I open a solution for the first time after it has been downloaded from TFS, it (Vs2010) is unable to find the NuGet.targets file.

I've checked TFS and it's marked as downloaded, and it exists on the file system.

If I try to open the solution directly from TFS again, it suddenly works.

I feel this is the reason why my automated builds are also failing.

Has anyone come across this issue before?

Stuart.Sklinar
  • 3,683
  • 4
  • 35
  • 89
  • Have you checked there's a .nuget directory in your solution's directory with the NuGet.targets file? The NuGet.targets is located using the $(SolutionDir) variable, I can't see any other reason than the file not being there locally... – Nock May 10 '12 at 12:00
  • Yup it's all there - as I said in my question - it all works fine, second time around... – Stuart.Sklinar May 10 '12 at 12:29

4 Answers4

10

Ran into this Friday and on another machine today.

For the machine on Friday I copied the .nuget directory, since I didn't have one.

For the machine today it had the .nuget directory and copying it from another machine didn't resolve the issue. Opening it from TFS's Source Control Explorer didn't work either.

We then followed the steps on Opening project in Visual Studio fails due to nuget.targets not found error (enable Package Restore on the solution) and it worked without issue.

Hadn't run into this before last week, and it's just one project of many, with none of the others having this problem.

Community
  • 1
  • 1
James Skemp
  • 8,018
  • 9
  • 64
  • 107
3

When Visual Studio downloads solutions from TFS (double click sln file in solution explorer) it appears to download files one by one and load them up. Unfortunately it seems to try opening project files before it downloads the .nuget directory, which is why it can't find the file. The last thing it appears to do is download that file, which explains why it is on disk but gave the error. If you reopen the solution it's already there and works fine.

When TFS Build server downloads a solution to build, it does so on the solution directory instead. Which means it will get the .nuget directory before it tries to build so it shouldn't cause issues on the build server.

I believe this is a bug in Visual Studio, it really should download all the solution items first. Although it would be nice if it had the same behaviour as TFS Builds.

A work around for this issue is to get latest on the solution folder before you open the solution for the first time. Not ideal but it works.

I'd also suggest logging a bug with either the nuget or visual studio team, however I suspect they're probably already aware of it.

Betty
  • 9,109
  • 2
  • 34
  • 48
2

I had this problem trying to run through the tutorial at http://www.windowsazure.com/en-us/develop/net/tutorials/multi-tier-web-site/2-download-and-run/

Turns out the zip file the source code was in extracts into a folder containing commas, which I don't think msbuild liked. Moving it into a more safely named directory helped.

John
  • 452
  • 2
  • 14
0

Try these steps

  1. Install Nuget.
  2. Right click on the solution and select "Enable NuGet Package Restore".
  3. Click Ok on the warning.
  4. Close and re-open the solution.
Rolwin Crasta
  • 4,219
  • 3
  • 35
  • 45