NuGet 1.4 Released

open source, nuget 0 comments suggest edit

The moon goes around the earth and when it comes up on the other side, Hark! There’s a new release of NuGet! Well, this time it was more like one and a half revolutions, but I’m happy nonetheless to announce the release of NuGet 1.4.

A big thank you goes out to the many external contributors who submitted patches to this release! Your enhancements are much appreciated!

I’ve written up much more details about what’s in this release in the NuGet 1.4 Release Notes, but I’ll highlight a few choice things in this blog post.

NuGet Self-Update Notification Check

One thing you may notice immediately if you’re running NuGet 1.3 today is that the NuGet dialog notifies you itself that there’s a new version of NuGet.

NuGet Update Check
Notification

Note: The check is only made if the Online tab has been selected in the current session.

This feature was actually added in NuGet 1.3, but obviously would not be visible until today, now that NuGet 1.4 is available.

Managing Packages Across The Solution

A lot of work in this release went into managing packages across the solution. If you’re a command-line junky, the Package Manager Console Update-Package commands now support updating all packages in all projects as well as a single package across all projects.

The NuGet dialog can also be launched at the solution level which makes it easy to choose a set of projects to install a package into, rather than installing a package into a project one at a time. This was a common request for those working on a large multi-project solution.

NuGet Project
Selection

What’s Next?

This blog post is just a tiny sampling of what’s new. Again, check out the release notes for more details.

We’re going to try better to have a roadmap of the next couple of releases hosted on the front page here: http://nuget.codeplex.com/. For now, it’s very high level and general because we really only fully plan one iteration ahead.

However, we do have an idea of some of the big themes we want to focus on:

  • Simple package creation: We constantly want to lower the bar for creating and sharing code from inside and outside of Visual Studio.
  • NuGet in the Enterprise:This includes CI scenarios outside of Visual Studio, authenticated feeds, etc.
  • Flexible packaging: Includes things like including assemblies that are not referenced but deployed and vice versa.
  • Developer Workflow: We’re looking at common workflows that don’t match our own expectations and how we can support them. This also includes workflows we do know about such as the use of pre-release packages etc.

In general though, I think we can sum up all of themes in one big theme: Make NuGet Better!

Get Involved!

If you have great ideas for NuGet, please get involved in the discussions. We try to be very responsive and we do accept external contributions as Joshua Flanagan learned and wrote about in his blog post, An opportunity for a viable .NET open source ecosystem.

Then, remembering my last experience, I figured I would at least start a discussion before giving up for the night. To my surprise, the next day it was turned into an issue – this isn’t just another Microsoft Connect black hole. After hashing out a few details, I went to work on a solution and submitted a pull request. It was accepted within a few days. Aha! This is open source. This is how its supposed to work. This works.

Onward to NuGet 1.5!

Found a typo or error? Suggest an edit! If accepted, your contribution is listed automatically here.

Comments

avatar

18 responses

  1. Avatar for Mike Brown
    Mike Brown June 17th, 2011

    Really excited about this. Nuget makes going from zero to fully working web app a breeze.
    install-package entityframework
    install-package MVCScaffolding
    install-package SqlCompactEdition
    Define my domain model and my secret sauce Scaffolding templates and boom boom boom. Add in some appharbor love with bitbucket and you've got a deployed app with continuous deployment in 10 minutes.

  2. Avatar for Andrew
    Andrew June 17th, 2011

    Your first release notes link has too many /'s after the http. Almost thought you hadn't posted them yet until I caught the extra / out of the corner of my eye

  3. Avatar for Kristof Claes
    Kristof Claes June 17th, 2011

    Nice!
    Is the feature to make it possible to exclude the packages folder from source control still on the to do list?

  4. Avatar for JayCee
    JayCee June 17th, 2011

    Please add an option to clearly display and filter trial and commercial packages.

  5. Avatar for Soul_Master
    Soul_Master June 18th, 2011

    One major thing that NuGet does not have is fully supporting source control. I think NuGet should automatically add all packages to solution folder name “packages”. So when we change/update package, project source control will automatically update source file too.
    Currently, I need to manually update all file in packages folder to source control.

  6. Avatar for Keith Brown
    Keith Brown June 18th, 2011

    The multi-project solution support was exactly what we needed. Kudos, guys!

  7. Avatar for Justin
    Justin June 19th, 2011

    I'm with Keith. Thanks for making it easier to manage packages across the solutions!

  8. Avatar for Rafael Teixeira
    Rafael Teixeira June 20th, 2011

    One thing I would love to see in 1.5/1.6: See a way to deploy p-invoked native libs alongside the dependent managed wrapper, currently that has to be added manually and fails on installation as the installer (the VS plugin) tries to scan the native lib like if it was managed.
    Another facet to this problem: bitness. Today NuGet has folders for specific frameworks/profiles but doesn't support sending two versions differing on bitness but targetted for the same framework.

  9. Avatar for roby
    roby June 20th, 2011

    Wyh it does'n install on visual studio 2010 Ultimated version?

  10. Avatar for chris
    chris June 20th, 2011

    Managing Packages at the Solution Level is exactly what we need! Good step forward.
    Pity about the problems with signing though:
    21/06/2011 12:36:00 - VSIXInstaller.SignatureMismatchException: The installed version of 'NuGet Package Manager' is signed, but the update version has an invalid signature. Therefore, Extension Manager cannot install the update.
    at VSIXInstaller.Common.VerifyMatchingExtensionSignatures(IInstalledExtension installedExtension, IInstallableExtension updateExtension)
    at VSIXInstaller.InstallProgressPage.BeginInstallVSIX(SupportedVSSKU targetAppID)

  11. Avatar for Dan
    Dan June 20th, 2011

    Phil,
    Why do we keep getting the invalid signature errors, shouldn't you guys have fixed this by now?

  12. Avatar for Marcelo Palladino
    Marcelo Palladino June 21st, 2011

    Great job Phil,
    Unfortunately, even after updating Nuget I'm still having problems with the company's proxy. What point exactly should I be informing the proxy credentials?
    Thanks in advance!

  13. Avatar for Chris Hohmann
    Chris Hohmann June 22nd, 2011

    I also encountered the invalid signature error again. I had to uninstall 1.3, then install 1.4. Not a big deal, but I would love to see this get resolved in the next release.

  14. Avatar for haacked
    haacked June 22nd, 2011

    As far as we can tell, the signing errors are occuring on Windows XP or Windows 2003 boxes due to a potential bug with the certificate authorities on those boxes. This is not a NuGet bug as far as we can tell. For example, most people were able to upgrade just fine.
    If you download our VSIX from 1.3 and 1.4 and compare them, you'll see that the signatures are correct.

  15. Avatar for bdaniel7
    bdaniel7 June 26th, 2011

    I'm quite new to NuGet and I added the sql server compact 4.0 to the project, via NuGet, but when I try to run the tests, I get "Unable to find the requested .Net Framework Data Provider. It may not be installed.". I go to Microsoft website, download and install Microsoft SQL Server Compact Edition 4.0, run the tests again and now it works. Now, my question is do I need to install SQL CE by hand? Why so, if the engine is only a file? Am I mistaken this CE with SQLite? Isn't NuGet supposed to take care of everything?

  16. Avatar for GONeale
    GONeale July 6th, 2011

    Hi Phil, I am not sure how much say you have over the direction of Nuget, but something I would love to see in future versions is the ability for me to specify which target framework version I would like of the package, eg. a command like 'install-package Ninject 4' for the .net 4 version, or better yet, based on the project I am installing the package to, it detects the target framework of the application. For instance when I install ninject I get all these folders:
    net35-Client
    net35-Full
    net40-Client
    net40-Full
    sl2
    sl3
    sl3-wp
    sl4
    Which is mostly redundant as I only use one of those assemblies, moreover this takes up a bunch of extra space (which then goes into TFS and downloaded to other developers).
    Has this been raised already? Let me know your thoughts,
    Graham

  17. Avatar for Dario Iacampo
    Dario Iacampo July 6th, 2011

    Do you think it could be possible/useful create a nuget package that makes a project ready for tdd?

  18. Avatar for haacked
    haacked July 13th, 2011

    @GONeal log a bug at the NuGet CodePlex website.