Coverage window is blank after VS Update about vsmac-codecoverage HOT 20 CLOSED

Hi,

Thanks for your feedback.
This is happening likely due to the extension not being compatable with the latest Visual Studio version.

I have just released version 1.2 of the extension built for the latest Visual Studio.
Updating to that extension should fix the issue you're seeing.

Regards,
Arthur

from vsmac-codecoverage.

This issue is resolved with version 1.1 of this plugin and VS for Mac 8.9.2 build 0

from vsmac-codecoverage.

Hi, same issue with VS 8.9.3 (build 13)

from vsmac-codecoverage.

Hi, Facing same issue with VS 8.9.3 (build 13)

from vsmac-codecoverage.

Also facing this issue with 8.9.5 (Build 4) on MacOS.
Actually, it works just after installation and a first restart so the pad appears in the menu. If I restart VS once afterwards, it is blank until I reinstall the plugin.

from vsmac-codecoverage.

Hello all. Thank you for your feedback on this issue.
I am looking into it shortly.

I believe this is caused by the extension being compiled specifying a specific version of the Unit Testing Visual Studio extension. Whereas any version should be fine for this extension.

I'll try and fix this once and for all as this is a recurring issue it seems.

from vsmac-codecoverage.

Just released a new version (v1.3).

Try it out. Should hopefully fix the issue once and for all.

Will keep this issue open until the next version of VS to see if another update will affect it.

from vsmac-codecoverage.

I have 1.3 plugin installed and VS 8.9.8.
Unfortunately, the coverage pan is blank.
It is first time I am using the tool.
I hope I did everything right.

from vsmac-codecoverage.

@DragonTM Thanks for letting me know.

I doubt you did anything wrong. This seems to be a recurring issue I cannot get to the bottom of.
Will look into it again and make a new version.

from vsmac-codecoverage.

Actually, I am having a bit of trouble replicating it this time round.

I have updated my VS to v8.9.8 and installed v1.3 of the extension and it worked right away.

Any chance anyone on this thread could try installing my other Code Distribution extension and let me know if that presents the same issue with the pad being blank after installing? It would help a lot in diagnosing this.

from vsmac-codecoverage.

New version out.

I have replaced the GTK UI with native OSX UI. I suspect that was having trouble.
We'll see if this fixes it.

from vsmac-codecoverage.

I'm having the same issue, but maybe a little different.

If I install the extension, and restart VS then it shows up fine.

If I restart VS after that then the pad is blank. I can't find anyway to get the Coverage pad to display properly again except to uninstall the extension (restart VS) and reinstall the extension (restart VS again). But then again it only shows once. Successive VS restarts won't show it.

from vsmac-codecoverage.

Looking a bit closer at @usjpaq 's original post.
It looks like the issue is actually that the extension cannot find the TestPlatform library when launching.

Which might make sense if its failing after a Visual Studio update.
Will try and include the library as part of the extension and see if that solves it.

from vsmac-codecoverage.

I see the same issue as @Qythyx with the coverage pad being blank. Whilst a VS update could be the catalyst for a problem, a definitely see the problem without an upgrade being involved. I switch between solutions a lot, and wonder if it's related to that. I can always get the extension back by an uninstall & reinstall cycle.
@ademanuele are there any specific logs I could look in to help diagnose the problem?

from vsmac-codecoverage.

@ademanuele I don't have the same issue with the Code Distribution Plugin. Also I've been using coverage a lot in the last couple of days, and have had the coverage window go blank without restarting, upgrading or switching solution.

from vsmac-codecoverage.

Thanks for the feedback guys.
I am also wondering if the specific solution that is loaded has something to do with this crash.
Its a hard one to analyse as it doesn't seem to happen when VS for Mac is hooked up to the debugger.

@usjpaq has provided very good stack trace info there, not sure how he got it though. Maybe you could enlighten us actually, I'd be curious to know how you got that stack trace out of VS. 😃

Looking at that though, it seems like an assembly can't be found. Which would be quite strange since it works on first launch.
I'll look at this issue some more today.

from vsmac-codecoverage.

So I figured out how to get that stack trace for the exception.
Help > Open Log Directory for people who are interested.

And yeah, I have been able to replicate this but not while connected to a debugger.
And from the log, it does seem like it can't resolve the assembly.
No idea why, that assembly should be offered by Visual Studio itself.

There is only one NuGet package with that name but its not made by Microsoft.
This SO thread seems to suggest there's this other Microsoft package that should have the assembly in there.
Adding that does not solve the problem.

SO this needs more investigation.
Not sure what to try next. Any suggestions are welcome. :D

from vsmac-codecoverage.

Right.

I think I got to the bottom of it.
My suspicion is that Visual Studio does not immediately try to load the extension on startup when the extension is newly installed. It'll launch it a few seconds after.

But then subsequent launches, it'll load it a bit sooner.
So I think that is happening is that Visual Studio is loading the Code Coverage extension before loading the Unit Testing extension in which the TestPlatform.ObjectModel assembly is provided.

Couldn't figure out how to solve that ordering if that is indeed the issue.

So I removed the dependency on the TestPlatform.ObjectModel.
Thankfully was not such a big job.

New version (v2.0.1) is out now.
Download it and let me know if you run into issues again.
I've tried launching and relaunching VS a good number of times and the pad launched just fine with the new version.

Alrighty then. Now for a stiff drink. 🥃

from vsmac-codecoverage.

The fix seems to have worked for me. Since upgrading the problem hasn't happened.

Thanks!!

from vsmac-codecoverage.

That's good to hear @Qythyx ! 😄

I'll close this issue. I'm fairly confident this issue is resolved now.
Thank you everyone for helping resolve it!

from vsmac-codecoverage.