FortuneN / FineCodeCoverage

Visualize unit test code coverage easily for free in Visual Studio Community Edition (and other editions too)
https://marketplace.visualstudio.com/items?itemName=FortuneNgwenya.FineCodeCoverage
Other
527 stars 40 forks source link

OutputToolWindowPackage did not load #276

Closed rcmosher closed 2 years ago

rcmosher commented 2 years ago

Installed product versions

Description

The following error shows if I try to open any Fine Code Coverage menu item (View > Other Windows > Fine Code Coverage, Tools > Options > Fine Code Coverage > General). In general Fine Code Coverage is not working.

The 'OutputToolWindowPackage' package did not load correctly.

The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file 'C:\User\me\AppData\Roaming\Microsoft\VisualStudio\17.0_57b64d9b\ActivityLog.xml'.

Restarting Visual Studio Could help resolve this issue.

Continue to show this error message?

Steps to recreate

  1. Attempt to open View > Other Windows > Fine Code Coverage
  2. Attempt to open Tools > Options > Fine Code Coverage > General

Current behavior

Error when trying to use Fine Code Coverage. Unable to get any coverage information.

Expected behavior

Should be able to access above menu items without error. Should get code coverage results.

tonyhallett commented 2 years ago

please can you add the relevant details of the ActivityLog.xml

It may be an issue that can be resolved with https://marketplace.visualstudio.com/items?itemName=MadsKristensen.ClearMEFComponentCache

rcmosher commented 2 years ago

I've added relevant ActivityLog.xml. I've also attached the MEF errors as FineCodeCoverage shows up a lot there (this was from a fresh run of VS with no project open). Clear the MEF Component Cache did not help.

147 Error Microsoft.VisualStudio.TestWindow.VsHost.TestWindowPackage Exception occurred while loading solution options: System.Runtime.InteropServices.COMException (0x8000FFFF): Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED)) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.VisualStudio.Shell.Package.Initialize() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)

This also seemed like it could be related:

147 Error Microsoft.VisualStudio.TestWindow.VsHost.TestWindowPackage Exception occurred while loading solution options: System.Runtime.InteropServices.COMException (0x8000FFFF): Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED)) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.VisualStudio.Shell.Package.Initialize() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)

MEF errors.txt

tonyhallett commented 2 years ago

The issue is with the version of the Visual Studio Sdk that FCC is using. If you can update visual studio I believe there should be no issues. ( regarding the loading of Microsoft.VisualStudio.Threading, Version=17.1.0.0)

I am currently working on a feature branch that has a dependency to the earlier version of the Visual Studio Sdk so as to prevent this issue / not forcing a visual studio version in the manifest.

rcmosher commented 2 years ago

Updating resolved the issue. Thank you @tonyhallett and thanks to all the contributors for this project!