NuGet exited with code -1 — Build failing as a result

Question

I have installed dotless via Package Manager in VS2012 in to an existing mixed C# solution (Class libraries and MVC2 apps), however now when I build it (F5) I get the following two errors:

The command ""C:\@GitRepos\EBS\SolutionFiles\.nuget\nuget.exe" install "C:\@GitRepos\EBS\\packages.config" -source "" -o "C:\@GitRepos\EBS\SolutionFiles\packages"" exited with code -1.

and

The system cannot find the path specified.

After adding dotless to the solution a ".nuget" folder with "NuGet.exe and "NuGet.targets" has been added.

I have also tried adding dotless to a new MVC2 project and other than having to add a mime type to the web.config it all works well. There isn't however a ".nuget" folder.

I also noticed that the same happens if I create a new NServiceBus solution (after installing it). The paths in the message change but the error is the same.

If I take

"C:\@GitRepos\EBS\SolutionFiles\.nuget\nuget.exe" install "C:\@GitRepos\EBS\\packages.config" -source "" -o "C:\@GitRepos\EBS\SolutionFiles\packages"

and run it via a command prompt then I get:

All packages listed in packages.config are already installed.

Answer 1

So after giving up on this and then a few days later looking in to it again, I found the answer. I came across david-martos.blogspot.co.uk. After opening my command prompt and finding it also said "The system cannot find the path specified" I went looking in the registry. I found in "HKEY_CURRENT_USER\Software\Microsoft\Command Processor" that there was an AutoRun key for "c:\ansi140\x64\ansicon.exe -p ". After deleting this and trying one of my NserviceBus solutions again I found it built fine. I hope this helps others.

Here is a direct link to David Martos post.

Answer 2

This was also likely a nuget package restore consent that you had to set. http://blog.nuget.org/20120518/package-restore-and-consent.html

For anyone who wants to permanently have the consent accepted, take a look at installing http://nuget.org/packages/NuGetEnablePackageRestore - it will be accepted on all machines automatically.

Answer 3

I solved this problem by opening up the Package Manager Console and clicking on the "Restore" button on the warning that popped up. Here's a pick of what it looked like. This is similar to the other solutions, but from a different angle.