Differences between aspnetcidev and aspnetvnext?

Question

What are the differences between aspnetcidev and aspnetvnext?

I see that aspnetcidev says "quick builds", but what does this mean?

Answer 1

Jan 29, 2016 edit:

This information is now part of the ASP.NET wiki: https://github.com/aspnet/Home/wiki/NuGet-feeds

---

The ASP.NET build system uses 3 myget feeds for each branch + nuget.org.

• aspnetvolatile<branch> (aspnetvolatiledev/aspnetvolatilerelease)
• aspnetci<branch> (aspnetcidev/aspnetcirelease)
• aspnetvnext (dev branch)/aspnetrelease (release branch)

After each repo under github.com/aspnet builds successfully, each package produced by it is pushed to the corresponding volatile feed.

After the graph of repos is build, we trigger the Coherence build. This build verifies that the packages have matching versions and their references are correct (that they are coherent). Then, it pushes them to aspnetci<branch>.

Once the Coherence build passes, we run all our tests on the packages in the aspnetci<branch> feed. If the tests pass, we sign the packages and ship them to aspnetvnext or aspnetrelease

So the differences are:

• aspnetvolatile<branch>

  • latest packages
  • possible not coherent
  • not tested
  • not signed
  • updated on every checkin
  • mostly used to diagnose build failure

• aspnetci<branch>

  • possible not latest
  • coherent
  • not tested
  • not signed
  • updated when all repos build successfully
  • used by our build system

• aspnetvnext/ (aspnetrelease|nuget.org)

  • possible not latest
  • coherent
  • signed
  • tested
  • updated when everything works
  • used for stable packages

Once the aspnetcirelease feed is stable, we push the packages from it to nuget.org.

Unless you work on developing new features for ASP.NET, I recommend that you use aspnetvnext (for dev bits) or nuget.org (for release bits). The release feed (aspnetrelease) is just a staging feed and it's not always in a good shape.

Edit:

I think it's easier to understand from a table:

Answer 2

I'm abrade that you can get the exact answer on the question only from Microsoft. You can open https://www.myget.org/gallery and filter for "aspnet" for example and will find many other repositories published for different teams.

For me more interesting is the information displayed by .NET Version Manager: dnvm (without parameters):

Thus, for me, the source https://www.myget.org/F/aspnetvnext/api/v2/ (or https://www.myget.org/F/aspnetvnext/api/v3/index.json) is the "official" place for the night builds of ASP.NET 5.

On the other side by filtering of https://www.myget.org/gallery "aspnet" you can see that aspnetvnext contains more distinct packages as aspnetcidev.

It's clear that both repositories probably contains different set of packages.

One important example where the repository https://www.myget.org/gallery/aspnetcidev be used is the new .NET Command Line Interface (.NET CLI) which you find on GitHub here. The new dotnet utility uses https://www.myget.org/F/aspnetcidev/api/v3/index.json together with many other sources in https://github.com/dotnet/cli/blob/master/NuGet.Config.

I suppose that AspNetCIDev is the repository of packages required for .NET CLI. It's the utility, which should replace dnx and dnu in RC2 of ASP.NET 5. See the post, this one and some other.