The post is here:
http://weblogs.asp.net/nunitaddin/archive/2006/02/01/437082.aspx#437183
In a nutshell, TD.NET 2.0.1343d is installed, as is NCover 1.3.3. I can
run the various "Test With..." commands, but "Test With...Coverage"
displays a version and compatibility message, but nothing else happens.
I'm using VS 2003 Pro on Windows XP SP2. I've been using TD.NET for
nearly a year and wanted to try it also with code coverage.
Any ideas?
> In a nutshell, TD.NET 2.0.1343d is installed, as is NCover 1.3.3. I can
> run the various "Test With..." commands, but "Test With...Coverage"
> displays a version and compatibility message, but nothing else happens.
>
> I'm using VS 2003 Pro on Windows XP SP2.
>
This is supposed to be a supported configuration. Are you running as
admin? Which directory is NCover installed in? NCover 1.3.3 doesn't
install a registry entry with its install dir. I make a guess that it
is here:
"%ProgramFiles%\NCover\NCover.Console.exe"
It will display the compatibility message if it can't find
'NCover.Console.exe' at that location.
Thanks, Jamie.
Before reinstalling, I discovered that the registry key,
HKEY_CURRENT_USER\Software\Code Mortem\NCover\InstallDir, was being
read, though it didn't exist. I created the key and pointed it to the
NCover installation folder, but NCover still could not be found.
Anyway, all's well, so thanks again.
> Thanks, Jamie, that was the problem. I reinstalled NCover to the
> default location, as you specified, and Test With...Coverage works now.
>
Excellent!
> Before reinstalling, I discovered that the registry key,
> HKEY_CURRENT_USER\Software\Code Mortem\NCover\InstallDir, was being
> read, though it didn't exist. I created the key and pointed it to the
> NCover installation folder, but NCover still could not be found.
>
This might actually confuse it. If 'InstallDir' is found,
TestDriven.NET will assume there's a new version of NCover installed
(1.5.1 or later). Otherwise it will look for a legacy (1.3) version of
NCover in the 'Program Files' directory. It will execute this using
different command line arguments.
Thanks, Jamie.