Hi,

Under VS2010, an upgrade of NCrunch (or any extension) causes VS to flush its package cache and rebuild this.

Because VS is not perfect, there are some situations where clearing out and rebuilding the cache can cause internal problems. This means that while it is unlikely NCrunch is responsible for a plugin clash, the installation may have triggered an unrelated problem.

I recommend trying the following command: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe /setup

This will rebuild VS2010's extension cache and configuration.

You can also try: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe /rootsuffix test

This will start VS2010 with a different registry hive. If the VS registry hive is corrupt, this will work around the problem.

In all truth, without solid indication that NCrunch is at fault here, it will be very hard for me to investigate this problem as all symptoms are pointing inside VS itself.