NuGet 1.3 Released

nuget, code, open source 0 comments suggest edit

In continuing our efforts to release early, release often, I’m happy to announce the release of NuGet 1.3!

Upgrade!If you go into Visual Studio and select Tools > Extension Manager, click on the Update tab and you’ll see that this new version of NuGet is available as an update. Click the Upgrade button and you’re all set. It only takes a minute and it really is that easy to upgrade.

Extension
Manager

As always, there’s a new version of NuGet.exe corresponding with this release as well as a new version of the Package Explorer. If you have a fairly recent version of NuGet.exe, you can upgrade it by simply running the following command:

NuGet.exe u

076583
fg1019

Expect a new version of Package Explorer to be released soon as well. It is a click once application so all you need to do is open it and it will prompt you to upgrade it when an upgrade is available.

There’s a lot of cool improvements and bug fixes in this release as you can see in the release announcement. One of my favorite features is the ability to quicky create a package from a project file (csproj, vbproj) and push the package with debugging symbols to the server. David Ebbo wrote a great blog post about this feature and Scott Hanselman and I demonstrated this feature 20 minutes into our NuGet in Depth talk at Mix 11.

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

Comments

avatar

13 responses

  1. Avatar for Fabian Vilers
    Fabian Vilers April 26th, 2011

    Great, but I thought these features were already in version 1.2, don't they?

  2. Avatar for Vizyon500k
    Vizyon500k April 26th, 2011

    Great Post Phil ;)

  3. Avatar for NickS
    NickS April 26th, 2011

    With every new release, I have to uninstall then reinstall NuGet due to certificate signing errors. Any way to avoid this going forward?

  4. Avatar for haacked
    haacked April 26th, 2011

    @NickS that shouldn't be the case. It's worked for me. Are you installing interim builds from our CI server by chance? Those are not signed so if you install any of those, you will have to uninstall first.
    If you only install the release builds (via VS Extension Gallery), they should upgrade just fine.

  5. Avatar for David Cumps
    David Cumps April 26th, 2011

    Can't update from VS 2010, due to this error:
    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.

  6. Avatar for Dave
    Dave April 26th, 2011

    I have the same issue as David Cumps. I'm wondering if this may have something to do with updating via the MVC Tools update.

  7. Avatar for Dave
    Dave April 26th, 2011

    It appears that NuGet was installed with elevated rights in VS2010 and was never updated when I installed the MVC tools update. I just uninstalled and reinstalled without the elevation and believe it will work fine next time.

  8. Avatar for Michael McGuire
    Michael McGuire April 26th, 2011

    Yeah, same here for me. Here's a snippet from the log if it helps:
    4/27/2011 8:03:47 AM - Verifying matching extension signatures before updating...
    Installed Extension Path: C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Microsoft Corporation\NuGet Package Manager\1.2.20325.9034\
    Update Extension Path: c:\documents and settings\___________\local settings\temp\tmp3830.tmp
    4/27/2011 8:03:47 AM - 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)
    4/27/2011 8:03:47 AM - Install Error : 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)

  9. Avatar for Dan Sorensen
    Dan Sorensen April 26th, 2011

    If we don't have NuGet.exe, where is the official place to find it?

  10. Avatar for haacked
    haacked April 27th, 2011

    @David, @Michael, which version of NuGet do you currently have installed? If you go to the Package Manager Console and type in $host, what does it tell you?
    @Dan, go to http://nuget.codeplex.com/releases to get the command line tool.

  11. Avatar for Donnie Hale
    Donnie Hale April 27th, 2011

    I had the same problem as David and Michael. Here's what I did to get 1.3 installed:
    - Download .vsix to local file system
    - Uninstall Nuget from Control Panel
    - Uninstall Nuget within VS 2010 (it still showed up there even after Control Panel uninstall)
    - Double-click the .vsix to install it
    Success!
    Thanks for everything, Phil.

  12. Avatar for RobertC
    RobertC April 27th, 2011

    I get the certificate invalid error too when I try to upgrade from extension manager. $host gives me version: 1.2.20325.9034

  13. Avatar for zhangzhao
    zhangzhao May 6th, 2011

    Hope one day we can use NuGet in sharepoint and vs2010 team foundation