New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: VS cannot load CM #496

casiosmu opened this Issue Oct 31, 2017 · 4 comments


None yet
2 participants

casiosmu commented Oct 31, 2017


  • Visual Studio version: 2012 Professional
  • CodeMaid version: 10.4.53
  • Code language: C#

Steps to recreate

  1. Installed VS2012 in a freshly setup Win7 ( a) including and also b) not including all Updates) (I think it doesnt matter, but Win7 is inside a VirtualMachine)
  2. let VS initialize environment to C#
  3. install CM via Tools->Extensions --> no error
  4. restart VS:
    Error-Popup: Cannot load CodeMaid package properly. The problem was maybe caused by a configuration change or installation of another extension. Also check %appdata%\Microsoft\VisualStudio\11.0\ActivityLog.xml (<--my own translation from german)
  5. as I write this VS offered "VisualStudio Update 5". But: the error still there after installation

Same message also appears when I click Menu->CodeMaid->anyItem

In the ActivityLog.xml I only can find 3 entries regarding CM (for each shown error):

  1. beginPackageLoad
  2. CreateInstance failed; 80121604; "A call target has caused an exception" (<--my own translation from german)
  3. End package load; 80004005 - E_FAIL

This happens in 2 different Win7 instances, both with the same VS2012.
There are only 3 pre-installed extensions, none I installed myself:

  • Microsoft Web Developer Tools 1.0.30710.0
  • NuGet Package Manager 2.0.30625.9003
  • VS Ext. for Windows Library for JavaScript 1.0.85140.

I tried uninstalling NuGet (the only extension I could uninstall), but the error persists.


This comment has been minimized.


codecadwallader commented Nov 1, 2017

Thanks for reporting the issue. Take a look at #437 or #489 .. maybe it's related to your .NET Framework version installed?


This comment has been minimized.

casiosmu commented Nov 2, 2017

Ok, the current .NET version is 4.5.51209.
After update to 4.6.1 the problem didnt occur again, also after update to 4.7. Thank you.

Btw: it would be nice, if you could add a "Required" section to your which lists things like that.

@casiosmu casiosmu closed this Nov 2, 2017

@codecadwallader codecadwallader added this to the v10.5 milestone Nov 3, 2017


This comment has been minimized.


codecadwallader commented Nov 3, 2017

Great idea, I'll actually reopen this idea as a reminder to do that with the next release. I'll also double check the dependencies.. looks like it still may say v4.5 in the manifest which would be mistaken.

@codecadwallader codecadwallader self-assigned this Nov 3, 2017


This comment has been minimized.


codecadwallader commented Apr 28, 2018

This was fixed in the manifest and will be present in the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment