How can 'nuget restore' download pre-release packages?

c# nuget build-process nuget-package nuget-package-restore
Aaron Cunnington picture Aaron Cunnington · Jan 30, 2014 · Viewed 10k times · Source

We are faced with an issue in our build environment where we would like for our continuous integration builds to download the 'latest and greatest' NuGet packages that are marked as pre-release by appropriately appending the version number with -dev.

Whenever we run the command nuget restore, it fails to pick up any pre-release versions. I have looked over the documentation on the NuGet Versioning page but it rather inconveniently omits details on how to add prerelease ranges to the allowed versions it should download in the packages.config file.

Currently, the packages.config file looks like this:

<?xml version="1.0" encoding="utf-8"?>
<packages>
  <package id="Foo" version="1.0.0" targetFramework="net35" />
</packages>

And we wish to be able for NuGet to at least be able to see and then to choose the latest version from a list like the following:

  • Foo.1.0.0-dev1401291727ef87505.nupkg
  • Foo.1.0.0-dev14012918064fdf488.nupkg

Unfortunately, no pre-release versions are seen, and only 'released' packages are used by the restore process. A typical error message when trying to download a pre-release only package would be:

Unable to find version '1.0.0' of package 'Foo'.

Is there some way that I can specify a range of versions that includes pre-release packages in the packages.config file? Or even from within the .nuspec file itself?

Many thanks in advance.

Answer

Matthew Skelton picture Matthew Skelton · Feb 6, 2014

There is no way AFAIK to specify to use pre-release packages within packages.config. Instead, use the -InstallPrerelease flag (PowerShell) or Prerelease flag (command-line nuget.exe) to specify that pre-release/beta packages should be installed in preference to stable packages.

Note that Foo.1.0.0-dev1234 is considered earlier than Foo.1.0.0, so if the the stable package exists (Foo.1.0.0) then any Foo.1.0.0-xxxx beta/pre-release packages will not be installed. In such a case, you'd need to up-rev the beta version to (say) Foo.1.0.1-devxxxx for it to be found as 'newer' than Foo.1.0.0.

See here for further details: How to publish nuget prerelease version package

Related questions

How do I enable NuGet Package Restore in Visual Studio?

There's a similar post on stack but it doesn't help with my issue possibly because I am using Visual Studio 2015. How do I get the "Enable NuGet Package Restore" option to appear in VS2015? I chose File > New Project …

Read More
System.MissingMethodException: Method not found?

What once was working in my asp.net webforms app now throws this error: System.MissingMethodException: Method not found The DoThis method is on the same class and it should work. I have a generic handler as such: public class …

Read More
Where can I find a NuGet package for upgrading to System.Web.Http v5.0.0.0?

Just upgraded an ASP.NET MVC4 project to use Unity.WebApi version 5.0.0.0 and it requires System.Web.Http v 5.0.0.0 as per the following error: Assembly 'Unity.WebApi, Version=5.1.0.0, Culture=neutral, PublicKeyToken=43da31bc42a85347' uses 'System.Web.Http, Version=5.0.0.0, …

Read More