Home → Problems →

Nuget restore behvior changed

• Edit

withoutprecedence

05 Sep, 2015 01:38 PM

I have begun seen build errors seemingly due to changes in the way the nuget restore command works. I have two solution level nuget packages which adds some tools I need. Something has changed without me doing anything, causing these packages to not be installed on the build server. To see the changes look at the following builds of the same commit:

Successful build:
https://ci.appveyor.com/project/MortenChristiansen/overflow-net/build/1.0.0-pre.3+8%20(Build%2069)

Failing build:
https://ci.appveyor.com/project/MortenChristiansen/overflow-net/build/1.0.0-pre.3+8%20(Build%2076)

The output looks quite different for the nuget restore command. In particular, these lines are relevant (and do not have an equivant in the failing build):

https://ci.appveyor.com/project/MortenChristiansen/overflow-net/build/1.0.0-pre.3+8%20(Build%2069)#L73
https://ci.appveyor.com/project/MortenChristiansen/overflow-net/build/1.0.0-pre.3+8%20(Build%2069)#L74

Has a new version of nuget been installed that works differently, or is there something else at play here?

1. Support Staff 1 Posted by Feodor Fitsner on 05 Sep, 2015 02:31 PM

   

   Right, it was nuget 3.1 installed on VS 2015 build workers. And seems like there is a bug with solution packages restore.

   You can always get back to a previous 2.8.5 version by adding this line to your build script:

   (New-Object Net.WebClient).DownloadFile('https://www.nuget.org/nuget.exe', 'C:\Tools\NuGet\NuGet.exe')
   

   Alternatively, you may try the latest nuget 3.2-rc which just released:

   (New-Object Net.WebClient).DownloadFile('https://dist.nuget.org/win-x86-commandline/v3.2.0-rc/nuget.exe', 'C:\Tools\NuGet\NuGet.exe')
   

   • Edit

2. 2 Posted by withoutpreceden... on 07 Sep, 2015 12:46 PM

   

   Thanks. 3.2 did not work, but the first option did.

   • Edit

3. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:59 AM.