Let me start with saying thank you, the tool is great, helps a lot!
Recently I started experiencing an issue whereby Visual Studio 2017 crashes, and upon restart it claims that the crash was caused by the Presto Coverage 1.16.6 extension.
The crash happens after running a coverlet command to update coverage info in c:\coverlet and (presumably) Presto picking up the changes.
Any ideas on how to resolve this?
Visual Studio is 2017 v15.9.15 and 15.9.16
Steps to reproduce:
Environment: I have two instances of VS 2017 running (A and B), with two different solutions open. Both have coverage reporting using Coverlet and Presto. Coverlet saves coverage info to c:\coverlet in bot solutions. Coverage json file names include project names, so no collision there.
"A" has a solution with stale coverage info (unit tests have not been executed for some time).
I execute unit tests in "B"
I run coverlet for solution "B" (updating coverage info in the shared location)
VS "A" crashes, stating that Presto extension is responsible, asking whether I want to disable it.
If I execute unit tests in solution "A" (in VS Test Explorer) take the same steps as above, VS doesn't crash.
Let me start with saying thank you, the tool is great, helps a lot!
Recently I started experiencing an issue whereby Visual Studio 2017 crashes, and upon restart it claims that the crash was caused by the Presto Coverage 1.16.6 extension. The crash happens after running a coverlet command to update coverage info in c:\coverlet and (presumably) Presto picking up the changes.
Any ideas on how to resolve this? Visual Studio is 2017 v15.9.15 and 15.9.16
Steps to reproduce: Environment: I have two instances of VS 2017 running (A and B), with two different solutions open. Both have coverage reporting using Coverlet and Presto. Coverlet saves coverage info to c:\coverlet in bot solutions. Coverage json file names include project names, so no collision there.