NuGet 1.2 Released

I’m happy to announce the release of NuGet 1.2. It took us a bit longer than we expected to get this release out there, and I’ll explain why later, but for now, go install it!

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 should be available as an update. It only takes a minute and it really is that easy to upgrade.

For more details about what’s in this release, check out the announcement on nuget.org.

There’s also a new version of NuGet.exe corresponding with this release as well as 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

Thanks to everyone who helped make this happen. I’ll be writing about our plans for 1.3 fairly soon. Smile

Comments

11 responses

All-In-One Code Framework • March 30th, 2011
Nice! Congratulations on the new release!!
Microsoft All-In-One Code Framework team looks forward to working with Nuget to share reusable source files

James L • March 30th, 2011
I had VSIXInstaller.exe has encountered a problem and needs to close.
It only worked when I unchecked the 'protect my computer' checkbox on the identity selection dialog.

James L • March 30th, 2011
I spoke to soon...
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.

David Fowler • March 30th, 2011
@James L
If you're running NuGet 1.0 you need to uninstall it and then install the new version of NuGet. See the list of known issues nuget.codeplex.com/wikipage?title=Known%20Issues

Johnny Oshika • March 30th, 2011
Oh oh. I get the following error when clicking "Add Library Package Reference...":
Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))
I even uninstalled and re-installed, but I still get the same error.
Thanks

ms440 • March 30th, 2011
The same installation error as James L:
3/31/2011 8:09:06 AM - The extension will be upgraded from version 1.1.229.160.
3/31/2011 8:09:11 AM - The following target products have been selected...
3/31/2011 8:09:11 AM - Microsoft Visual Studio 2010 Ultimate
3/31/2011 8:09:11 AM -
3/31/2011 8:09:11 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.1.229.160\
Update Extension Path: c:\documents and settings\michael shapiro\local settings\temp\tmp120d.tmp
3/31/2011 8:09:11 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)
3/31/2011 8:09:11 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)

NickS • March 31st, 2011
I also experienced the SignatureMismatchException while going from NuGet 1.1 -> 1.2 (I had previously seen the same error when upgrading from 1.0 -> 1.1).
Uninstalling and re-installing (with the 'protect my computer' checkbox unchecked) did work, and I now have NuGet 1.2.20325.9034 installed.

John • March 31st, 2011
VS Gallery Site is down, we can NOT download any Extension package.

Tim Savage • April 5th, 2011
Awesome, have been fully embracing NuGet in my company.
We have one fiddly issue you may be able to enlighten us on (or do a post!). How to build a NuGet package that supports multiple framework versions to be created from a project file.
We have managed to automate creation of NuGet Packages for a single framework version, including updating of package version to match current assembly version without a problem but the multiple versions in one build has stumped us.
Cheers!

Levi Bailey • April 14th, 2011
I'm getting started with NuGet and want to create a package. I have a need for my package to transform the web.config file in the Views directory for MVC projects. How can this be accomplished, I've only seen examples of transforming the main web.config. Thanks for any information.

haacked • April 15th, 2011
Did you try putting a Web.config.transform in the Content\Views\ directory of your package?