Error when importing code coverage file on VS Community
See original GitHub issue---------------------------
Microsoft Visual Studio
---------------------------
Exception was thrown: Could not load file or assembly 'Microsoft.VisualStudio.Coverage.Analysis, Version=15.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
---------------------------
OK
---------------------------
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Error when importing code coverage file on VS Community
Error when importing code coverage file on VS Community #2392 ... Exception was thrown: Could not load file or assembly 'Microsoft.
Read more >Troubleshoot code coverage - Visual Studio
Code coverage isn't run, and either the code coverage window doesn't open at the end of the test run, or it shows old...
Read more >Can't open .coverage file without Test Explorer winowd open.
I downloaded a code coverage results file from Azure DevOps Build Pipeline and when I click on Import Results in the Code Coverage...
Read more >Code Coverage Not working for Visual Studio Test results
A .coveragexml file was created but not imported by Azure Dev Ops or Sonar Cloud. When we try to open them in Visual...
Read more >Error with SonarQube Visual Studio Code Coverage Import
I am seeing errors when importing Coverage results from one specific solution. Others seem to work fine. I have been using version 5.1...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@huguesv can you please link to issue forwarded to Code Coverage team, if there is one?
Nothing for us to fix, it’s up to the code coverage team now.