More fun with NCover and TypeMock integration

Hello everyone,

First, thank you for your patience, and thanks to all who posted tips/tricks on this subject. I have attempted most of them (the ones that seem to apply), but have had no luck yet.

We have a somewhat unique situation: our build server is not under our control. Our company is organized so that there is a separate SCM team and Development team, and the SCM team is also in a geographically different location. We are not, at this time, attempting to integrate Ncover/Typemock with our build server. However, our local management is interested in tracking code coverage statistics. It has fallen to me to make this happen.

Before we began using Typemock, I was able to generate all of the code coverage reports I needed with NCover through a simple command line. I developed a standalone console app that dynamically determines which of our apps-under-development I'm interested in generating statistics for. It then generates the proper command line text and shells out to a new process to perform the task itself.

This command line no longer works, because we now need to run NCover through Typemock runner. I've been experimenting with no luck whatsoever. Below is the command line code that is generated.

"c:Program FilesTypemockIsolator.0TMockRunner.exe" -first -link NCover3.0 "C:Program FilesNCover
cover.console.exe" "C:Program FilesMicrosoft Visual Studio 10.0Common7IDEMSTest.exe" /testcontainer:C:_SourceLibraries_UnitTestsCommonApp.UnitTestsinDebugCommonApp.UnitTests.dll //h "\remotemachineDataCoverageReportsCommonApp" //at "C:datacoverageCommonApp	rends.trend" //x "C:datacoverageCommonAppcoverage.xml" //l "C:datacoverageCommonAppcoverage.log" //ll "Normal" //onlywithsource //pm "vstesthost.exe" //p "CommonApp Code Coverage" //ssp "Registry, SymbolServer, BuildPath, ExecutingDir"

The above code actually executes all of the tests as expected. However, it always results in "No data was collected", so I wind up with absolutely no coverage results.

Additionally, I get the infamous exit code #20000. I've repaired my installation a number of times, and used the Isolator Configuration to link the NCover 3.0 profiler (incidentally...it doesn't seem to persist this linkage from execution to execution....).

Any help you can offer would be greatly appreciated!

- Nat