The 'CoverageExtPackage' package did not load correctly.

[cbigurra]

Hello, I'm experimenting an issue with the extention.

I'm using VS 2017:

I just followed the guide of installation and when I try to 'Run code coverage' I got the following message:

I tried reinstalling all my VS suit and the extention, but it as the same behavior.

Do I need to install other thing or may I missing anything?

Thanks!

[atlaste]

What's in the XML? There should be an exception and stacktrace.

[cbigurra]

I'm sorry, I don't have it right now, but when I get it again, I'll share it here ;)

[cbigurra]

What's in the XML? There should be an exception and stacktrace.

Hi,

I got this:
CreateInstance failed for package [CoverageExtPackage]Source: 'mscorlib' Description: Could not load file or assembly 'Microsoft.VisualStudio.Shell.15.0, Version=16.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Shell.15.0, Version=16.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.VisualStudio.Shell.15.0, Version=16.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
 at System.Reflection.RuntimeAssembly.GetType(RuntimeAssembly assembly, String name, Boolean throwOnError, Boolean ignoreCase, ObjectHandleOnStack type)
 at System.Reflection.RuntimeAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
 at System.Activator.CreateInstanceFromInternal(String assemblyFile, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo)
 at System.AppDomain.CreateInstanceFrom(String assemblyFile, String typeName)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].


[atlaste]

Interesting, Microsoft.VisualStudio.Shell.15.0 is just part of Visual Studio. On my pc you it's in C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\PublicAssemblies . Can you check?

[cbigurra]

Interesting, Microsoft.VisualStudio.Shell.15.0 is just part of Visual Studio. On my pc you it's in C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\PublicAssemblies . Can you check?

Hi, thanks for the answers!

I checked the Microsoft.VisualStudio.Shell.15.0 and it doesn't exists, I'm using the professional edition; I don't have the path you mentioned, I have installed C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\PublicAssemblies.
What should I do, should I install the Community edition?

[atlaste]

Community and pro are basically the same except for intended use.

Anyways, i think i can device a small workaround, will make a new version tomorrow at the office.

[atlaste]

Sorry for the late reaction, I kinda forgot about this issue. Anyways, I've just taken a look, without much progress I'm afraid.

This appears to be this issue: https://stackoverflow.com/questions/46054343/visual-studio-2015-fail-to-load-package-because-microsoft-visualstudio-shell-15 and it is described in detail what to do here: https://docs.microsoft.com/en-us/archive/msdn-magazine/2017/august/visual-studio-creating-extensions-for-multiple-visual-studio-versions . Unfortunately I currently don't have the time to go through that, otherwise I would have fixed it.

Alternatively, you might just try an older version that targets 2017 specifically, like this one: https://github.com/atlaste/CPPCoverage/blob/cda640167703cad7e0ff18ce363f686dc68c5a27/CoverageExt/CoverageExt.vsix and see if that does the trick for you.