This project is read-only.

Nightly build packages on MyGet

Topics: General
Apr 28, 2012 at 3:12 AM
Edited Apr 28, 2012 at 3:14 AM

We've just finished up a task which will be uploading nightly signed NuGet packages to MyGet. If you want to try out our daily builds (made from the "master" branch in Git), this is the place to do it!

The feed URL is:

Some things to consider:

  • There is no guarantee of new packages every night.
    We are uploading these at the end of our nightly build, and if the nightly build fails for some reason, then there will be no packages.
  • There is no SemVer (i.e., the packages are not marked as "pre-release").
    Our WebStack v2 build process predates NuGet's support for SemVer versioned packages, and once you've started down a pre-RTM path without SemVer, you can't go back. We may fix this in v.Next.
  • There is no guarantee of longevity.
    We reserve the right to pull packages from the MyGet feed as we see fit. Using NuGet package restore with these is not recommended, unless you're going to keep copies around locally for yourself. In addition, we reserve the right to move the pre-release packages to if/when we start using pre-release versioning, so this URL may not be around forever.
  • There is no source or symbols.
    Our current build process does not create a symbols or source package. We may fix that at some point in the future.
  • There is no support.
    These packages will be the equivalent of you having pulled the source and built them yourself, but with the advantage of the packages being signed, so you should be able to use them on a machine without SkipStrongNames installed.
  • There will be bugs.
    The code compiles, and the unit tests pass, but that's it. Otherwise, it's what's in the tree, and it may not work. If you find a bug, great! Report it. And when we fix it, then that night's package should unblock you.

Enjoy! :)

Apr 28, 2012 at 7:35 AM

Awesome sauce! :)

May 9, 2012 at 10:36 PM

So if you're like me, you just spent 15 minutes figuring out nu get syntax.   Just to shorten the process for others...

update-package AspNetWebApi     -IncludePrerelease -source

May 10, 2012 at 1:00 AM

better yet just add as a respository source by going into the Nuget settings then you can select that repository and do an update-package on the console it will update all of the aspnetstack bits for mvc without having to do the individual packages...


May 10, 2012 at 4:08 AM
May 20, 2012 at 1:01 PM

is there a stable version after the Beta?
relying on Beta in our production is one thing, but relying on nightly builds that are not stable is quite another thing...

Also what are the major differences between the beta and the currently nightly build? 

May 20, 2012 at 10:43 PM

Hi ozba,

We're working on a stable release right now that we're putting some of the last touches on. The Beta and the most recent builds have quite a lot of changes in them. But from the latest nightly build until the final RTM build there will not be major changes. It'll be mostly bug fixes, and some limited API changes.



May 20, 2012 at 10:43 PM

The RC drop is not too far away so that will be the next stable drop. You can see the branch here [1]. We'll be sending out a README with that release detailing the changes.




May 21, 2012 at 10:45 AM

Thank you eilonlipton and HenrikN!

So we will be waiting for the RC drop that will come soon as you say.

Where will you announce it so we won't miss it, and do you have an estimation when will it be release? in a matter of days, month, 2 months?

Thanks again! 

Aug 31, 2012 at 11:32 AM

Sorry to be a drag, what's the SemVer thing all about? A pre-release marked package is a good thing because?

Aug 31, 2012 at 9:09 PM
It's good because it won't offer to upgrade people away from stable RTM builds. They must opt in to the non-RTM builds. This will become even more important when we release pre-release milestone builds on