Any ideas of why my Nuget Package Manager Console suddenly does not load (greyed out)?
I have tried opening the console from within different contexts/projects without luck.
If it was to throw an error on console startup, where could I catch possible error messages? Output window is empty.
I am using Visual Studio 2013 Premium with Nuget Package Manager v2.8.
Reinstalling Nuget fixed this issue.
I am, however, still unaware of what caused such behavior.
Hiding the console window is what grayed it out for me... I uninstalled/reinstalled Nuget package and then I restarted VS and it came back :)
Related
I just completed a fresh install of Visual Studio Enterprise 2015.
When I run Visual Studio, go to Tools > NuGet Package Manager, and select 1 of the 3 options (Package Manager Console, Manage NuGet Packages for Solution or Package Manager Settings), nothing happens. The menu closes and no windows appear.
When I go to Options > NuGet Package Manager, I get "An error occurred loading this property page."
I have tried uninstalling and re-installing NuGet Package Manager from Extensions and Updates, but this doesn't solve the problem. I have also downloaded NuGet.Tools.vsix and when I run this, it tells me that the extension is already installed to all applicable products.
I don't know if I'm missing a setting that enables the Package Manager in Visual Studio, or if this problem is caused by something else...
Un-install Nuget Package that came with Visual Studio 2015 RTM ( Tools->Extensions and Updates).
Re-install latest (3.1.60 or >) Nuget Package Manager Visual Studio Extension ( from Online)
Then you can open without errors or silently failing
I just came across the same issues as Sean, I found that updating to the latest version of the package manager (3.1.60724.766 at time of writing) seemed to resolve the issue.
Yea npm is buggy in 2015 remove dependency check when installing and it should work.
I had exactly the same problem that sean described. Uninstalling NuGet and installing the newest version from the website did not seem to have any effects.
But this way worked for me:
I went to Windows' Control Panel where you can uninstall software. Visual Studio 2015 has a repair option there. I tried it. The repair dialog recommended to update the repair routine first. So I updated, that needed a few minutes. After this I let the repair routine run. It needed something like one and a half hour. And then the problem was away!
This turned out to be a permissions issue that I encountered after the VS installation. I'm not sure if it was a bug in VS or something that is exclusive to my network account settings.
I have been trying to find a solution for this since almost 3 days, but i'm stuck and cant figure out why the Nuget package manager is just not opening, it does not even give any error.
Things i have tried so far:
Uninstalled and re-installed the nuget package manager from within VS 2012 but it didnt work
Uninstalled and re-installed Visual Studio 2012 and then tried the above step once again, but still nothing happened.
When i navigate to Tools -> Library Package Manager -> and click on all the options listed in it, nothing opens, no sign of any error etc.
Can someone please help me with a workaround for this problem.
Download and install it from
https://visualstudiogallery.msdn.microsoft.com/27077b70-9dad-4c64-adcf-c7cf6bc9970c
or
https://nuget.codeplex.com/downloads/get/784776
I tried to create a tool window for visual studio 2013 Update2. I did File->NewProject->Visual Studio Package and inside the wizard I checked Tool Window. Then I pressed F5 and I saw my tool window inside the Exp instance of VS under View->OtherWindows. Yeah, it is working!!!
Then I created a new package with proper names. Unfortunately at the moment I am not able to Debug, Load or even install the package on normal visual studio instance. Just nothing happens. No errors, no exceptions, no tool window option showing under View->OtherWindows. I can clearly see the package under Tools->Extensions and Updates....
I tried to:
Uninstall and Install again
Clear all cache under \AppData\~..~\Extensions\ and \AppData\~..~\ComponentModelCache
Create another package. May be I did > 20 packages with defaults
Restart PC
Clear all records in registry for already installed packages
All possible combinations of the steps above
What else I could try? Ideas?
PS: I forgot to mention that I have latest Roslyn installed.
When I start visual studio express 2012 for web I get this error in the package manager console.
Cannot load Windows PowerShell snap-in Microsoft.PowerShell.Core because of the following
error: Unable to load one or more of the requested types. Retrieve the LoaderExceptions
property for more information.
Loader Exceptions:
Exception of type 'System.OutOfMemoryException' was thrown.
I don't remember adding anything new to visual studio. I searched other related problems but they don't work for me.
I tried repairing visual studio. I also tried re-installing visual studio which temporarily removed the problem but it is back again.
Anyone has a solution?
I finally made it work. I suspected it is something from windows update that messed up with my VS since I didn't really add anything to VS. I am not sure which updates to remove so I just uninstalled all the windows update that starts in a certain date. Here are the actual steps that I did:
What I did is uninstalled visual studio 2012 express for web following this tutorial.
And then uninstalled windows updates starting from the date I believe the error started appearing.
After I used CCleaner to clean my registry. Had to run it 2 times to just to make sure it is clean. I'm not sure if this actually helps. I just heard from my friend that uninstalling applications sometime leaves registry keys behind.
Finally, I installed visual studio again. Package manager is back to normal.
Restarted my laptop and it is still working. So I guess it is solved.
I think System Restore would do solve this instead of doing all this steps. But system restore was not an option for .
When i try to access my solution Properties, i get the following error:
Object reference not set to an instance of an object
I am using VS 2012. What could be the cause of this?
Some extensions may cause this.
Try disabling extensions and restarting Visual Studio.
Quite often error will be gone even if you re-enable extensions after this.
There's a bug report on Microsoft Connect (link).
It is marked there as "Closed as External", but it seems that it may occur randomly with any extension, so would be worth voting it there to bring it to Microsofts attention.
In my case, the problem was solution-specific. NuGet was causing this error, but not the extension itself but a NuGet package that generated an error on VS load. When I opened NuGet Package Manager Console I saw a big red text with a description of the error. In my case it was T4Scaffolding.Core package, which in turn is a dependency of MVCMailer.
If this is your case, you will probably see what package generates an error in PM Console.
I faced this dialog too and i'm not sure what exactly causes this as i couldn't even open the NuGet console to see detailed error messages.
Closing Visual Studio, deleting %AppData%\Microsoft\VisualStudio and restarting Visual Studio worked for me as it causes a reset of various things like window configurations.
I think if this dialog is displayed some files may be corrupt in %AppData%\Microsoft\VisualStudio and by deleting that folder Visual Studio can start normally again.
Update:
The issue arises on my machine when i start Visual Studio by using "run as administator" whereas Visual Studio has been started before without that option and %AppData%\Microsoft\VisualStudio had been created without the administator association.
Visual Studio 2013: I had this issue when I tried opening TOOLS -> Extensions and Updates.
I used #ViRuSTriNiTy idea, but only cleaned the files from:
C:\Users[myUserName]\AppData\Local\Microsoft\VisualStudio\12.0\Extensions
There are 2 cache files over there.
Deleted them and restarted VS2013 and it was fixed
The way it was happening for me might be unique to me/my setup, but I'd love to know if anyone else has this happen, and if they find out why:
If I launch an .sln file by double-clicking it, it will load VS and I can right-click the Solution and get Properties to come up no problem.
If I go to "Open Project" on the Visual Studio welcome page or from File > Open > Project/Solution, navigate to the .sln file and launch it by selecting it and clicking "Open" in the File dialog, that's when I have this issue.
I'm going to just always launch the .sln file from now on, but I'd love to know why this happens when using "Open Project" from the welcome page or from File > Open > Project/Solution! I tried going into Tools > NuGet Package Manager > General and I unchecked the options for allowing NuGet to download missing packages and Skip applying binding redirects, and under Package Sources I de-selected the checkboxes (my dev machine does not connect to the internet). Environment > Extensions and Updates: I tried it with and without "Load per user extensions when running as administrator" and running it as an Admin and without running as Admin. Also tried just deleting everything at C:\Users\me\AppData\Local\Microsoft\VisualStudio. No change from those 2 bullets above.