NuGet CTP 2 Released!
My team has been hard at work the past few weeks cranking out code and today we are releasing the second preview of NuGet (which you may have heard referred to as NuPack in the past, but was renamed for CTP 2 by the community). If you’re not familiar with what NuGet is, please read my introductory blog post on the topic.
For a detailed list of what changed, check out the NuGet Release Notes.
How do I get it?
There are three ways to get NuGet CTP 2.
Via MVC 3
NuGet CTP 2 is included as part of the ASP.NET MVC 3 Release Candidate installation (install via Web PI or download the standalone installer) . So when you install ASP.NET MVC 3 RC, you’ll have NuGet installed.
Via the Visual Studio Extension Gallery
If you want to try out NuGet without installing ASP.NET MVC 3 RC, feel free to install it via the Visual Studio Extension Gallery.
As with all of our releases, we also make the download available on our CodePlex website.
As the release notes point out, we’ve made a lot of improvements. Some of the big ones are changes to the NuSpec package format, so if you have any old .nupkg files laying around, you’ll need to build them with the new CTP 2 NuGet.exe command line tool.
But to be nice, we already updated all the packages in the temporary feed which is at a new location now, so you won’t need to do that. But if you’re building new packages, be sure to update your copy of Nuget.exe.
The NuSpec format now includes two new fields you should take advantage of if you are creating packages:
iconUrlfield specifies the URL for a 32x32 png icon that shows up next to your package entry within the Add Package Dialog. Be sure to set that to distinguish your package.
projectUrlfield points to a web page that provides more information about your package.
Another big change we made is that the package feed is now an Open Data
Protocol (OData) Service Endpoint. This
makes it easy for clients to write arbitrary queries using LINQ against
IQueryable interface which is automatically translated to the
proper query URL. For example, to see the first 10 packages that start
Also, when using the Powershell based Package Manager Console, be sure
to note that we renamed the
Add-Package command to
Remove-Package command to
Uninstall-Package. We felt the new
names conveyed the right semantics.
So far, the project has been a lot of fun to work on, in large part due to the enthusiasm and excitement that we’ve seen from the community. As I mentioned in the past, this is truly an Open Source project and we’ve had quite a few community code contributions.
Of course, we still have plenty of items up for grabs if you’re looking for something to work on.
One cool thing we’ve done is integrated the use of ReviewBoard for doing code reviews into our process. For information on that, check out our code review instructions. Our review board is currently hosted at http://reviewboard.nupack.com/ but that domain name will change soon.
For those of you who like life in the fast lane, we do have a Team City based Continuous Integration (CI) server hosted at http://ci.nuget.org:8080/. You can get daily builds compiled directly from our source tree. So for those of you who knew about the build server, you would have been playing with the CTP 2 for a while now.
Well our next release is going to be NuGet version 1.0 RTM. A lot of our focus for this iteration will be on applying some spit and polish as well as integration work on our sister project, Gallery Server.
The Gallery Server project is building what will become the official gallery for NuGet (as well as for Orchard modules and other types of galleries). It’s being developed as an Open Source project as well so that anyone can take the source and host their own galleries.
Once the gallery server is completed and hosted, we’ll start to transition from our current temporary feed over to the gallery server. We’ll leave the temporary feed up for a while to allow people time to transition over to whatever the final official gallery location ends up at.
At this point, if you haven’t tried NuGet, give it a try. If you have tried it, let us know what you think. I hope you enjoy using it, I know I do.