Great idea to solve the problem of installing pre-requisites on developer PCs. Removes the barrier to using non-standard components. Package Manager idea is clearly taken from the Linux world, probably the only good part of that, LOL. Good to see this used in a positive way in the Windows world.
Just rename it from NuGet to something sensible like "Visual Studio Package Manager". Those cryptic Linux style names have no place in the clean world of MS products and technologies :-). The command should be named to say what it does on the tin; then what is a "Nu"?
Can't install the update like everybody else (no test before release??) but I cannot remove the current version either. I've removed NuGet via add/remove programs in Windows, but in Visual Studio the options to disable or remove NuGet are greyed out..
So please fix this!
update: you must run Visual Studio as administrator to be able to uninstall NuGet.
Why the heck do you put detailed instructions on how to fix the Visual Studio 2010 Ultimate update problem, instead of just posting a new fixed version? Would have saved the customers a lot of trouble I presume... But otherwise, really awesome extension, a must have :)
1. Uninstall "NuGet" from Programs/Features 2. Open Visual Studio as an Administrator (i.e. right click, "Run as Administrator") 3. Go to "Tools" --> "Extension Manager" and uninstall NuGet from Visual Studio
After that, you should be able to install the new VSIX from here.
Lot of errors in trying to update to lastest version... Poor Microsoft, this is the beginning of the end! Thanks goes to Kid 5x1llz who found the undocumented solution...
- Go to Program and Features, search for "Nuget" and uninstall it - Go to Visual Studio > Toole > Extension Manager > Find Nuget and uninstalll it - Restart
I also got this error when installing. It is confusing as you may be lead to believe it is an issue with VS2010. However, it is an issue with the NuGet installer itself.
Here is how I resolved it: - Go to Program and Features, search for "Nuget" and uninstall it - Go to Visual Studio > Toole > Extension Manager > Find Nuget and uninstalll it - Restart
Attempt to re-install it and you should be good to go.
Of course, none of this is documented, the error message isnt even clear and worst you may not realize you have Nuget installed! Very annoying time waster.
I have tried to use the NuGet Manager inside of VS 2010 Ultimate running on Windows 7 Ultimate 64 bit and it comes back with an error stating it cannot install for my version of VS 2010 Ultimate. Please add this version to the package checking for upgrading.
Sometimes the Package Manager Console fails to load the NuGet module therefor any command will fail to execute and throw an error such as "The term 'Install-Package' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again." to solve it just run the module manually like so.
import-module "c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Microsoft Corporation\NuGet Package Manager\1.6.21215.9133\Modules\NuGet\NuGet"
Make sure you get the path right.
I have "invalid child element 'NuGetToolsPath'" in code.
Re-installed latest NuGet did not help.
PM> nuget update
The term 'nuget' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that
the path is correct and try again.
I tried the recommended fix:
PM> import-module "c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Microsoft Corporation\NuGet Package Manager\1.6.21215.9133\Modules\NuGet\NuGet"
Import-Module : The specified module 'c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Microsoft Corporation\NuGet Package Manager\1.6.21215.913
3\Modules\NuGet\NuGet' was not loaded because no valid module file was found in any module directory.
At line:1 char:14
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Micro
soft Corporation\NuGet Package Manager\1.6.21215.9133\Modules\NuGet>dir
Volume in drive C has no label.
Volume Serial Number is A412-9D17
Directory of C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Ex
tensions\Microsoft Corporation\NuGet Package Manager\1.6.21215.9133\Modules\NuGe
t
02/06/2012 04:19 PM <DIR> .
02/06/2012 04:19 PM <DIR> ..
02/06/2012 04:19 PM 2,010 about_NuGet.Cmdlets.help.txt
02/06/2012 04:19 PM 48,780 NuGet.Cmdlets.dll-Help.xml
02/06/2012 04:19 PM 21,583 NuGet.Format.ps1xml
02/06/2012 04:19 PM 12,509 NuGet.psd1
02/06/2012 04:19 PM 22,215 nuget.psm1
02/06/2012 04:19 PM 13,725 NuGet.Types.ps1xml
02/06/2012 04:19 PM 14,644 Profile.ps1
7 File(s) 135,466 bytes
2 Dir(s) 12,749,586,432 bytes free
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Micro
soft Corporation\NuGet Package Manager\1.6.21215.9133\Modules\NuGet>
Not working.
VS2010 run as admin
???
Anyone else getting "The specified account doesn't exist. (Exception from HRESULT: 0x80070525)" when you try to install? I don't get this problem with any other extension.
Tried installing as myself and as Administrator, same error both times.
Bah!
Jon 1001, I'm getting the same error trying to upgrade from 1.5.20902.9026. Afterwards, under Tools|Library Package Manager, I had only Package Manager Console and Package Manager Settings. The console opened to the old version. Then I went into Programs and Features and unistalled NuGet, and re-ran NuGet.Tools.vsix, and again it failed to install with the message that "The specified account does not exist.". I'm not sure what to try next.
the update doesn't install, below a line from the log file
all Error : VSIXInstaller.SignatureMismatchException: The signature on the update version of 'NuGet Package Manager' does not match the signature on the installed version. Therefore, Extension Manager cannot install the update.
I solved it using the instructions on other comments below.
Here's what you need to do:
- Start VS in admin mode
- Go to Extension Manager and uninstall NuGet
- Restart VS
- Start VS
- Go to Extensio Manager and install new version of Nuget
This worked for previous versions but this time going from 1.5 to 1.6 failed and the uninstall/disable are disabled... tried to remove it using the control panel.. it says it did but the install still fails and vs says its still install. Any sugestions?
Hi,
is this extension work on Visual Studio Express 2010 ? I can't find NuGet in Extension Manager, when i try install by website then i receive error:
"This extension is not installable on any currently installed products."
I'm using the Entity Framework Migrations package, and it was installed before upgrading from Nuget 1.5 to Nuget 1.6 -- but now the commands built into that package (like "Add-Migration") do not work in the package manager console. They act as if they're not found.
If I remove the migrations package and re-install it, the commands start working again.
Seems like a bug in 1.6?
Still seems like a bug in 1.6, there's another workaround apparently: http://social.msdn.microsoft.com/Forums/en-US/adonetefx/thread/19d40fd2-d127-4d45-93d2-e4624e1b19be
The signature on the update version of 'NuGet Package Manager' does not match the signature on the installed version. Therefore, Extension Manager cannot install the update.
12/12/2011 6:28:09 PM - VSIXInstaller.SignatureMismatchException: The signature on the update version of 'NuGet Package Manager' does not match the signature on the installed version. Therefore, Extension Manager cannot install the update.
Okay, uninstalled and reinstalled per their what's new (really, Microsoft?)
Second issue, now all requests in NuGet show a "500" Internal Server Error.
Nicholas598305 : how did you uninstall it?
The both the 'Disable' and 'Uninstall' buttons are disabled on when I go to Extension Manager|Installed Extensions?
Thanks swingtownusa - just found that little 'Nugget' (pun intended) buried in the docs.!
Uninstall and reinstalled succesfully...
Where are you geting the 500 error; when you try to add a package
I can successfully -ListAvailable...
Run VS2010 as Administrator and the NuGet uninstall button will be available.
Then, install new version via Tools > Extension Manager, and you're good to go.
Good luck.
Not sure the upgrade from 1.2 to 1.6 works either. Attempting an installation on VS 2010 Premium sp1 using VS Extension Manager. Control panel does not display any version of NuGet to unistall. My only option is update in VS Extension Manager. Looking at the log file, VS Premium is not a supported edition. Version NuGet 1.2 was installed before the SP1 upgrade.
My question is simple has anyone running VS Premium SP1 installed or updated NuGet 1.6? If so what magical steps were performed. I have trimmed the log file, 2000 character max!
Thanks!
Log File:
12/14/2011 3:41:58 PM - Microsoft Visual Studio Extension Installer
12/14/2011 3:41:58 PM - Name : NuGet Package Manager
12/14/2011 3:41:58 PM - Version : 1.6.21205.9031
12/14/2011 3:41:58 PM - Supported Visual Studio Editions :
12/14/2011 3:41:58 PM - Version : 10.0
12/14/2011 3:41:58 PM - Pro
12/14/2011 3:41:58 PM - IntegratedShell
12/14/2011 3:41:58 PM - VWDExpress
12/14/2011 3:41:58 PM - VPDExpress
12/14/2011 3:41:58 PM - Version : 11.0
12/14/2011 3:41:58 PM - The extension will be upgraded from version 1.2.20325.9034.
12/14/2011 3:42:01 PM - The following target products have been selected...
12/14/2011 3:42:01 PM - Microsoft Visual Studio 2010 Premium
12/14/2011 3:42:01 PM - VSIXInstaller.SignatureMismatchException: The signature on the update version of 'NuGet Package Manager' does not match the signature on the installed version. Therefore, Extension Manager cannot install the update.
So, VS2010 Extension Manager says there is an update for NuGet. I click "Update", and the download and install begins, all is well, except the installer requires VS2010 to be closed, which I cannot since its running the friggin update. How can u not have tested for such an event before releasing the update?
For upgrade to 1.6:
1. Run VS as Administrator
2. Go to Extension Manager under Installed Extensions, look for NuGet Package Manager and you will see the Uninstall button enabled.
3. Uninstall version 1.5, restart VS
4. Go to Extension Manger under Online Gallery look for the new version 1.6 and Install it.
5. Enjoy
When I set up our own in-house package source (using version 1.5), I'm getting an error from the main page (not the package source service URL which appears to work fine).
http://nuget.<ourdomain>/: CS0117: 'Helpers' does not contain a definition for 'GetPushUrl'
http://nuget.<ourdomain>/nuget works fine for serving packages within Visual Studio.
error is coming from Default.aspx, line 31
Line 29: <% } %>
Line 30: <blockquote>
Line 31: <strong>nuget push {package file} -s <%= Helpers.GetPushUrl(Request.Url, Request.ApplicationPath) %> {apikey}</strong>
Line 32: </blockquote>
Line 33: </fieldset>
We were running version 1.4 without issues but when someone tried to create a new package, they created it with a version that was no-longer compatible with 1.4 (which, by the way, took down the entire NuGet service) so we had no choice but to upgrade if we wanted that new package published.
Anyone else seen this or have a solution already?
This is keeping us from seeing the "You are running NuGet.Server v<whatever>" page. Its not a show-stopper but makes me worried that something else more serious may be lurking in our setup.
Free
