Nuget Restore via build server “unable to find version”

Question

I have a VS solution and as part of a TeamCity Build, we restore packages from both a private NuGet feed (myget) and the public feed (nuget.org). Most packages restore fine, but

Answer 1

The reason why the build failed, was an old version of nuget.exe. I finally solved this problem by downloading the latest version and put this executable in the Program Files x86 folder. Then I created a new system variabele to point to this executable. After that I add a NuGetInstaller package in my TFS Build Definition to let me configure TFS using this new NuGet.exe. This link helped me to let TFS use this new NuGet version

Answer 2

Using an old version of Visual Studio's Nuget

• Visual Studio has C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\Nuget.exe. Jenkins was using that to nuget restore
• Updated Nuget in program files,

  C:\Program Files (x86)\NuGet> ./nuget.exe update -self
  

• Pointed Jenkins at that new Nuget path and

Answer 3

According to THIS current document as of this writing from MS, the proper url is: https://api.nuget.org/v3/index.json

So I went about to fix the issue because I assumed it had nothing to do with the URL. I did 2 things, not sure which it was that resolved the issue but I'll post both here in case it helps someone.

• Within TFS2018 and within my build step for the installation of Nuget I specified version 4.9.3 (the reason I chose 4.9.3 because I noticed by looking at detailed log of VS that during my build it was using this version) and chose to always download the latest version.

• Second thing I did was I removed a Nuget.Config file from my project that was left over from something I was testing. Then I re-commited my changes to TFS

After I did both of the above steps the rest of my build started working.

Answer 4

Try using https://www.nuget.org/api/v2instead of https://api.nuget.org/v3/index.json per the nuget docs: https://docs.nuget.org/consume/Command-Line-Reference.

Answer 5

I ran into this problem with one of our build slaves leveraging TFS and Visual Studio.

The way I fixed it was, I opened the solution that wasn't compiling in Visual Studio, right-clicked on the SLN and selected "Enable Restore NuGet Packages"

That prompts a dialog box that you have to accept. After you've done that, you might be good to go. Right-click on the SLN again and run "Restore NuGet Packages", and if that operation succeeds, you're golden.

There's probably some setting you can adjust programmatically when setting up your slave environments, but that's one direct way to fix this kind of problem.

Answer 6

I followed this: https://blogs.msdn.microsoft.com/tfssetup/2017/04/18/tfs-2017-update-1-nuget-restore-task-always-fails-trying-to-find-packages-even-though-they-exist-on-the-feed/

I had tried 3.3 and got this error:

Restoring NuGet package Microsoft.AspNet.WebPages.3.2.3. WARNING: Unable to find version '3.5.0.2' of package 'Antlr'.

I downloaded the latest NuGet 4.3.0.4406 and set the Custom path to NuGet and that failed as well.

Surprisingly when I switched to 3.5 it worked.

If you are really stuck, run the command in a Command Line Prompt and it will work:

C:\Program Files (x86)\NuGet\nuget.exe restore -NonInteractive E:\agentXYZPool\_work\1\s\xyz.sln