NuGet Package Manager

Microsoft Free

A collection of tools to automate the process of downloading, installing, upgrading, configuring, and removing packages from a VS Project.

Microsoft
(330) Review
Visual Studio
2012, 2010
Download (8,437,925)
4/2/2014
2.8.50313.31
View
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (330)
Sign in to write a review
Sort by:

by ripper951 | March 14 2013

Cant install update because of singnature issues. Is there a resolution to this?

3/14/2013 1:05:07 PM - 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.

Microsoft - Visual Studio Platform Team April 25 2013
| Edit |
Delete

Please look at the workaround here for known issues: http://docs.nuget.org/docs/reference/known-issues#Upgrading_to_latest_NuGet_from_an_older_version_causes_a_signature_verification_error.

by marcal1 | March 01 2013

Very, very helpful tool.

by roadie133 | February 28 2013

After reading some of the reviews here I decided not to chance any install of this file, I do enough configuring, don't want to cause myself problems over a database view, so I sought for an answer elsewhere. Here it is:

http://www.codeproject.com/Articles/501625/How-to-configure-local-Nuget-Repository

Here is a command line option:

http://docs.nuget.org/docs/Reference/Package-Manager-Console-PowerShell-Reference

by Jürgen Röhr | February 26 2013

@PascalJoyeux: yes that happens. To me it feels like 1/2 of the updates.

@NuGet team: The usual work around of uninstalling and reinstalling does not work, as the uninstall button is disabled (installed version 2.2.31210.9045).

Any idea?

Cheers
Jürgen

EDIT:
@oliiscool: Thanks. Forgot to run as admin.
@all: Rating changed. Useful tool except for the update procedure

by oliiscool | February 22 2013

@-bera-, @Jürgen Röhr, @PascalJoyeux (and anyone who can't upgrade due to a signature mismatch):
1 - Run Visual Studio as an administrator.
2 - Tools > Extension Manager...
3 - Select NuGet Package Manager and the [Uninstall] button will now be enabled.
4 - Uninstall the extension.
5 - Restart Visual Studio when prompted.
6 - Download from this page the new version.
7 - Install the VSIX.

by -bera- | February 21 2013

...
21.02.2013 08:17:57 - VSIXInstaller.SignatureMismatchException: Die Signatur der Updateversion "NuGet Package Manager" stimmt nicht mit der Signatur der installierten Version überein. Daher kann das Update nicht vom Erweiterungs-Manager installiert werden.
bei VSIXInstaller.Common.VerifyMatchingExtensionSignatures(IInstalledExtension installedExtension, IInstallableExtension updateExtension)
bei VSIXInstaller.InstallProgressPage.BeginInstallVSIX(SupportedVSSKU targetAppID)
21.02.2013 08:17:57 - Installationsfehler: VSIXInstaller.SignatureMismatchException: Die Signatur der Updateversion "NuGet Package Manager" stimmt nicht mit der Signatur der installierten Version überein. Daher kann das Update nicht vom Erweiterungs-Manager installiert werden.
bei VSIXInstaller.Common.VerifyMatchingExtensionSignatures(IInstalledExtension installedExtension, IInstallableExtension updateExtension)
bei VSIXInstaller.InstallProgressPage.BeginInstallVSIX(SupportedVSSKU targetAppID)

by cogaritis | February 20 2013

Error installing?! What!? Oh, Microsoft authored it? That makes sense.

by Jaap Mosselman | February 20 2013

Excellent tool for adding functionality to your projects!
One wish: on the updates tab, show not only the latest version number, but also the version of the currently installed package.

(BTW: never have had any problems with installing and updating this extension, as mentioned below. I use always the latest version already for more than a year)

by PascalJoyeux | February 19 2013

Hi,

actual update does not work because of signature conflicts... Has anyone experienced the same? VS 2020 Pro...

Cheers,
Pascal

by Zentropicus | February 17 2013

A needed tool that works, more or less. The less part is the persistent problems it continues to have. A big favorite is the inability to implement proper updating because of key signature problems. This has been going on since the beginning... Here again, February 2013, its broekn again. Please fix it. Another issue is that it gets confused and loses track of the libraries its managing. This happens infrequently, thank Buddha, but when it does it screws things up pretty good. It should be advertised as perpetual beta and used with extreme caution on any non-trivial project.

Microsoft - Visual Studio Platform Team April 25 2013
| Edit |
Delete

can you please take a look the known issues list here for the fix: http://docs.nuget.org/docs/reference/known-issues#Upgrading_to_latest_NuGet_from_an_older_version_causes_a_signature_verification_error.

by Kasper Holdum | February 17 2013

by AlfredRA | February 17 2013

by MigueLito92 | February 14 2013

can i use it on VS 2010 c# express edition?

by jpe123 | February 14 2013

Installed perfectly...GREAT extension, really helps. Thanks!

by RohitArora | February 08 2013

Great Extension!

by TGoodhew | January 29 2013

by Dmitry Gurinovich | January 29 2013

Great extension! I'm using it in every project.

by Fokko Veegens | January 25 2013

by John Bowlin | January 10 2013

Fails to install the Extension. Install tries to call hundreds of vsixinstaller.exe until all memory is used up. I third this observation that 2 others have already mentioned. This is on VS 2010 SP1.

by Richard Clafton | January 04 2013

Those having issues with the SSMS error and failure to install...

If you have redirected your Documents folder then this is probably the cause.

Edit the registry:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\Personal

Change the entry from the folder you redirected to back to: C:\Users\[youruser]\Documents and you will probably find it works.

If you look in the C:\Users\[yourusers]\Documents folder before hand you will also no doubt see folders relating to VS201x.

Worked for me. It also fixed installation issues with other VSIX packages.

I found this using Process Monitor from the SysInternals suite. Mark Russinovich is a lifesaver!

Regards

Richard

61 - 80 of 330 Items