ResourceManagerPackage - package did not load correctly

Question

I'm having a problem with VS2015 and cordova projects. Earlier in the day my project was working great. However, I moved a project to a new folder and now VS2015 is not working well. It's running, but somehow webessentials was uninstalled, NPM package in my gulpfile.js corrupt Visual Studio ....

Anyone encounter this problem before?

  <entry>
<record>28</record>
<time>2015/09/22 22:18:17.610</time>
<type>Error</type>
<source>VisualStudio</source>
<description>Loading UI library</description>
<guid>{2EF1EC52-C8BF-4FE0-8ECE-BA9C0D5D1603}</guid>
<hr>800a006f</hr>
<errorinfo>Cannot find the requested resource: 'VSMenus.ctmenu'.</errorinfo>

<entry>
<record>48</record>
<time>2015/09/22 22:18:18.186</time>
<type>Error</type>
<source>VisualStudio</source>
<description>CreateInstance failed for package [ResourceManagerPackage]</description>
<guid>{7C6A3AE5-F469-4D51-B52D-50393DEC9432}</guid>
<hr>80070002</hr>
<errorinfo>Could not load file or assembly 'Microsoft.VisualStudio.Azure.ResourceManager.Contracts.1.0, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.</errorinfo>

Answer 1

Renaming or deleting the VS profile folder in the AppData profile directory fixed the issue for me. You might prefer renaming in case you have a lot of extensions installed if this solution does not resolve the issue and would like to revert by renaming the folder back.

[drive]:\Users\<your user>\AppData\Roaming\Microsoft\VisualStudio\14.0

Answer 2

Open REGEDIT and lookup into the registry to find the key {7C6A3AE5-F469-4D51-B52D-50393DEC9432}, as shown in the log file, the key should be under [User]\Software\Microsoft\VisualStudio\14.0_Config\AutoLoadPackages

You can delete it. Make an export first in case something goes wrong.

Answer 3

It happened to me after installing new version of VS 2015 Azure Pack.

Uninstalling all Azure components from 'Programs and Features' with today's install date and running the setup again helped.

Answer 4

I had a similar issue using Visual Studio 2017:

when trying to "add a reference" to a project.

The issue was resolved by uninstalling a previous version of Visual Studio (2012) installed on my computer.

Answer 5

This worked for me:

1. Close Visual Studio instances
2. Rename C:\Users\leibbr\AppData\Roaming\Microsoft\VisualStudio\14.0
3. Open Visual Studio (problem is gone, but so is TFS setup etc)
4. Close Visual Studio
5. Delete newly created 14.0 folder and rename old folder back to 14.0
6. Open Visual Studio
7. Magic!