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
522 stars 40 forks source link

Error 'FineCodeCoverage2022' Description: Could not load file or assembly 'Microsoft.VisualStudio.Threading' #319

Closed ptletski closed 1 year ago

ptletski commented 1 year ago

Installed product versions

Description

Fine Code Coverage window is not presented. Selecting Find Code Coverage in View/Other Windows menu presents error dialog stating that "the 'OutputToolWindowPackage' package did not load correctly."

Steps to recreate

  1. Install Fine Code Coverage from MarketPlace
  2. Start VS.
  3. Open View/Other Windows menu.
  4. Select Fine Code Coverage menu item.

Current behavior

Log content: SetSite failed for package [OutputToolWindowPackage]Source: 'FineCodeCoverage2022' Description: Could not load file or assembly 'Microsoft.VisualStudio.Threading, Version=17.1.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.Threading, Version=17.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'Microsoft.VisualStudio.Threading, Version=17.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' at FineCodeCoverage.Output.OutputToolWindowPackage.InitializeAsync(CancellationToken cancellationToken, IProgress1 progress) at Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass20_0.<b__1>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e) at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck) 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].

Expected behavior

Fine Code Coverage should be accessible.

Side Notes

tonyhallett commented 1 year ago

Please update Vs version