No Test Result / Code Coverage markers with 1.40 on 2012 RC

Installed addons:

- Resharper 7 EAP
- dotCover 2
- Nuget
- VSCommand Preview

Hope that this helps.

Also the nCrunch windows are yet not compatible with the dark VS 2012 theme.

Thanks for your great work.

Hi, thanks for posting!

Are you able to submit a bug report with this issue? It sounds like an exception is being thrown somewhere under the hood.


Thanks!

Remco

Remco wrote:Hi, thanks for posting!

Are you able to submit a bug report with this issue? It sounds like an exception is being thrown somewhere under the hood.


Thanks!

Remco

Nothing is shown unfortunately (with catch all Exception in VS turned on), is there an option to turn on NCrunch exceptions?

I will try a "uninstall all add-ons one-by-one" session later today.

Thanks for your quick reply.

You can turn on the 'Log to output window' option under the 'All Solutions' option inside the NCrunch configuration. When the log verbosity is set to Summary, NCrunch will only report critical information in the output window (i.e. exceptions).

If you choose the NCrunch->Submit Bug Report option from the VS menu, it will also send through a log file to me so that I can investigate the problem. Make sure to put a link to this forum thread in the bug report so that I know it's from you.

Thanks!


Remco

I've heard reports that uninstalling and reinstalling NCrunch seems to resolve this problem. I'm currently working on introducing a proper fix for it.

I've introduced a new revision of 1.40b to the download page including a speculative fix for this issue. I haven't yet reproduced it on my end, but hopefully the fix should resolve it. Please let me know if you see this issue again!

I sent a bug report now. I uninstalled, opened file in solution, closed and reinstalled - still no change.

No worries, it's all just RC after all :-).

I've finally managed to reproduce this problem on my end. After adding an extra step to the upgrade instructions, the problem seems to have resolved itself. Give it a try if you have time, I'd really like to know if this solves the problem for you. Supporting an RC can be frustrating at times, but a surprising number of people are already relying on the pre-release versions of VS2012 ... and this does also need to work when VS2012 is eventually released.