Cannot connect even though using //reg

Cannot connect even though using //reg

Hi!

I use the NCover Community Edition Version 1.5.8 beta (the current download). And I have problems to connect to the process. I use the following command:

"NCover.Console.exe "G:\Projekte\LogViewer\tools\NUnit\bin\net-2.0\nunit-console.exe" "G:\Projekte\LogViewer\build\FileParser.Tests.dll" //reg"

And this is the console output:

NCover.Console v1.5.8 - Code Coverage Analysis for .NET - http://ncover.org Copyright (c) 2004-2006 Peter Waldschmidt

"Command: G:\Projekte\LogViewer\tools\NUnit\bin\net-2.0\nunit-console.exe Command Args: "G:\Projekte\LogViewer\build\FileParser.Tests.dll" Working Directory: Assemblies: Coverage Xml: Coverage.Xml Coverage Log: Coverage.Log

Waiting for profiled application to connect...NUnit version 2.5.10.11092 Copyright (C) 2002-2009 Charlie Poole. Copyright (C) 2002-2004 James W. Newkirk, Michael C. Two, Alexei A. Vorontsov. Copyright (C) 2000-2002 Philip Craig. All Rights Reserved.

Runtime Environment - OS Version: Microsoft Windows NT 6.1.7601 Service Pack 1 CLR Version: 2.0.50727.5448 ( Net 2.0 )

ProcessModel: Default DomainUsage: Single Execution Runtime: Default .Hello Tokenizer!

Tests run: 1, Errors: 0, Failures: 0, Inconclusive: 0, Time: 0,0970194 seconds Not run: 0, Invalid: 0, Ignored: 0, Skipped: 0

Connected Profiled process terminated. Profiler connection not established."

Also I've tried all sorts of other parameters, eg //a But nothing works! What am I doing wrong?

Thank You for help!

SeboStone


RE: Cannot connect even though using //reg

I run the command on a 64bit system with .NET 4. Now I used Now I use the "nunit-console-x86.exe", this works!


RE: Cannot connect even though using //reg

Glad you got your coverage going, and thanks for posting!

NCover Support