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.
Related
First of all, I am trying to open a support request with Microsoft about this issue, but their support reporting portal isn't working. I have resorted to Stackoverflow because I have no way of getting to Microsoft.
Yesterday, I started updating Visual Studio 2022 from Visual Studio Installer by mistake and paused it shortly after. Today, I tried to open a project but Visual Studio seemed unavailable. At that point I remembered about the paused update and re-opened the Visual Studio installer. I tried to Resume, and I got the below error. The Modify and Remove options give out the same error too. There is no Repair option.
Sorry something went wrong
The dependent package of
'Microsoft.VisualStudio.Debugger.Concord,version=17.1.33203.90,productarch=x64'
cannot be found: Microsoft.VisualStudio.DebuggerClient.Concord,
version=[17.0,18.0].
I also tried Restarting and deleting temporary files using the Disk Cleanup tool - no difference.
I have tried to force an uninstall from the Add or Remove programs but this still redirects me to the Visual Studio installer.
I have tried to research this error online but found nothing.
I did not fix the issue but at least I managed to uninstall the Visual Studio instance to be able to start from scratch again. If you do not want to go down the route of uninstalling, feel free to try the steps as suggested by #garbagecollector.
I deleted the installation folder for 2022 from ProgramFiles.
I deleted the Visual Studio installer from Add or Remove programs. (Note: This actually uninstalled a working version of Visual Studio 2019 that I had, and left the messed up version of 2022 with the same issues, so beware if you do not want to uninstall another working version of Visual Studio)
Then I ran InstallCleanup.exe via CMD (in admin mode). Refer to the "Remove All with InstallCleanup.exe" section within this article. This seems to have cleared all Visual Studio related files including the Visual Studio
installer, and I could re-download the installer for Visual Studio
2022 Community edition and start afresh.
I faced the same issue today and could solve it by removing corresponding dependencies from _package.json files from C:\ProgramData\Microsoft\VisualStudio\Packages\[PACKAGE_NAME] folders.
I am not sure whether you can repair your installation this way, I tried only with uninstall.
So in your case edit this file:
C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualStudio.Debugger.Concord,version=17.1.33203.90,productarch=x64 and remove the line marked with "-->" under "dependencies":
{
"id": "Microsoft.VisualStudio.Debugger.Concord",
...
"dependencies": {
...
--> "Microsoft.VisualStudio.DebuggerClient.Concord": "[17.0,18.0]"
}
}
In my case I had to repeat this procedure for three or four _package.json files.
Quite new to SSIS. To open existing SSIS packages in Visual Studio and I clicked SSIS but it has opened Visual-Studio and not my packages.
In solution explorer showing that SSIS packages(incompatible) and below that "the application not installed",but actually in Extensions windows its showing that installed SSIS. Please help me out resolve the below error (Image).
I tried to modify the package and uninstalled the SSIS tool and installed again. But still same problem
I had the same problem and I found this menue choice in Visual Studio. I right clicked the Solution, chose Resolve Errors and it resolved my problem.
I think you need to install SQL Server Data Tools for you to launch the project and test in your local SQL instance. If you're, like me, fairly new to SSIS package, I suggest you follow this Microsoft official tutorial so that you are familiar with ins and outs of SSIS package.
If you are sure that you have installed all necessary components, please ensure that VS > Tools > Extensions and Updates > Microsoft Integration Services Projects is enabled. Once enabled, restart Visual Studio. It might still look the same. Last step is to right-click on the project and choose "Reload Project".
I always ignore and shut down the carking update notification when opening SSIS, until I encountered this error.
I tried googling it and tried "reload project" and "Resolve errors" option, I also uninstalled SSDT and reinstall it, I also disabled and enabled SSIS in "Extensions and Updates" Bar. They all failed.
So I updated SSIS since I'm bored and tired, then I tried "reload project" and "Resolve errors" option again, the magic is everything going fine, like before! It's just my experience, not representative.
I already faced the same problem, for some reasons the SSIS extension was disabled.
So to resolve this issue you need to go to :
Extensions > Manage Extensions > Installed
Make sure that the SSIS extension is enabled then close and reopen you project.
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.
Visual Studio 2012 will not allow me to set multiple startup projects.
I have tried:
Right-click the solution / Set StartUp Projects...
Result: Nothing happens.
View / Property Pages
Result: Popup "Object reference not set to an instance of an object."
I have no add-ins running, and disabled all extensions that can be disabled without uninstalling. Active extensions are
Microsoft Web Developer Tools
NuGet Package Manager
Visual Studio Extensions for Windows Library for JavaScript (1.0.8377.0 AND 1.0.9200.20512
VisualSVN
Is this a known issue? Is there a fix/work-around? Can I specify the startup projects by editing the .sln/.csproj file if the VS2012 UI continues to fail?
I'm pretty sure this has to do with NuGet Package Manager. I did as described here.
Uninstalled NuGet Package Manager in Tools => Extensions and Updates... and restarted Visual Studio 2012/Visual Studio 2013 Preview. Now I can happily configure my solution properties again!
Installed NuGet Package Manager again and the problem reappeared. :(
This is a palliative answer. If there's a definitive answer, please share it! :)
Make sure you vote on this Connect Bug.
Found this post while searching for a related issue I was having. I thought it would be helpful for others to know what I found.
My problem was trying to switch between start up projects, IIS Express would always load the same project. My solution was to edit the project properties >Web> assign a different port number for each project. Now when I select Set as StartUp Project... it actually works
Note** I did not have any issues with NuGet probably because I'm using the released version of 2013