Reputation:
When build my solution, I got an error:
Error 116 The command "nuget install “C:\Mycode\Test\some\ClassLibs\WCF\ServiceHosts\Monitor\packages.config” -o “C:\Mycode\Test\Some\ClassLibs\WCF\ServiceHosts\Monitor\packages.config”" exited with code 9009
I use VS 2012, Thanks.
Upvotes: 16
Views: 31048
Reputation: 271
To resolve the 'nuget exited with code 9009' error, I downloaded the newest version of NuGet.exe (https://www.nuget.org/downloads) and placed it in the C:\Windows directory so Windows could find the executable.
Upvotes: 23
Reputation: 4388
Error 9009 means that Visual Studio cannot find an executable - typically one used in a pre or post build step. In this instance, it seems that NuGet is the source of the problem.
Is it possible that you are using a solution that manages dependencies using NuGet (and probably has the "Enable NuGet package restore" option enabled), but you haven't yet loaded the NuGet extension into Visual Studio 2012?
To confirm if this is the case, go to the Tools menu, and click "Extensions and Updates", select installed and type nuget
Return into the search box at the top right corner of the Extensions and Updates form. If it's installed, you should see it listed with a version number - for example 2.4.40116.9051 which I believe is the most recent release as I type this. If you don't find it, select "online" from the list on the left hand side of the Extensions and Updates form. Locate the NuGet Package Manager entry (quite possibly the first item on the list) and click "download" to grab it.
Upvotes: 17