Setup Problems

No coverage indicators in latest release?

Started by macdonag on 15,819 views

Hi

I just upgraded to the latest version of NCrunch !1.44) and now my coverage line indicators are missing. I'm using VS2012. This worked on Friday! My project is building and is instrumented, according to the NCrunch project settings.

Uninstalling and reverting to 1.43 fixes the problem.
Hi, thanks for posting!

I received a bug report detailing the same issue. Was this report from you?

The problem is caused by an adornment layer bug in Visual Studio that sometimes surfaces while upgrading NCrunch. Essentially, it's an installation/setup problem. Uninstalling v1.43 and upgrading to 1.44 again should hopefully solve the problem - otherwise, have a read of the installation troubleshooting steps described in the documentation.


Cheers,

Remco
We are having this same issue at my office. Two of us use NCrunch and we cannot get the line indicators in 1.4.4 to work. We tried the installation troubleshooting steps, uninstall, delete folder, run the devenv.exe /setup and re-install but it did not remedy the issue. Our hearts are heavy with sorrow and our eyes drooping for lack of little green circles.
Hi,

I've identified the cause of this issue. It seems that the 1.44 had an installer issue that was preventing the package from being fully loaded, which prevented the adornments from being shown. The symptom of the problem is identical to an setup issue that affects roughly 0.1% of all installs (which can usually be corrected by reinstall), which caused some big confusion on my side. I'm very sorry for the trouble caused by this.

v1.44 on the download page has been updated to a later revision that includes a fix for the installer issue. If you redownload and reinstall 1.44, the issue should be resolved.


Cheers,

Remco
Remco wrote:Hi, thanks for posting!

I received a bug report detailing the same issue. Was this report from you?

The problem is caused by an adornment layer bug in Visual Studio that sometimes surfaces while upgrading NCrunch. Essentially, it's an installation/setup problem. Uninstalling v1.43 and upgrading to 1.44 again should hopefully solve the problem - otherwise, have a read of the installation troubleshooting steps described in the documentation.


Cheers,

Remco


It wasn't me - I just posted on the forum. Glad to hear it's being fixed.

Graham
The update worked for me.
Having tried everything listed here, still no code coverage markers.
Hi Xophias,

Can you let me know exactly which version of NCrunch you're running? (i.e. check under NCrunch->About).

If you can submit a bug report, I can then check this to see if you are experiencing a different issue with the same symptom.


Cheers,

Remco
1.44.0.11. As you say, I'll submit a bug report.
Hi Xophias,

I haven't managed to catch your bug report yet, but meanwhile, I'm wondering if you might be able to try the following:

1. Uninstall NCrunch entirely from your system (all versions for all versions of Visual Studio)
2. Ensure that the directory '\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Remco Software' and all its contents are completely deleted.
3. Run the following command: \Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe /setup
4. Wait for devenv.exe to finish its work (kill it after 15 minutes if it doesn't stop)
5. Reboot your computer
6. Load up Visual Studio 2010 and open any solution
7. Close down Visual Studio
8. Install the latest version of NCrunch
9. Run the following command again: \Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe /setup
10. Wait for devenv.exe to finish its work (kill it after 15 minutes if it doesn't stop)

... Then load up VS2010 again to see if the problem is fixed.

Previously where this issue has surfaced, it's been a Visual Studio configuration problem where the IDE somehow confuses the adornment layers between extensions. Performing a completely clean reinstall of NCrunch should reset the adornment layers and will usually solve the problem. I'm keen to hear if this does the trick!

Cheers,

Remco
Okay, that fixed it. Thanks :)

Post a reply

Log in to reply.