NCover, UI Testing and //pm

I looking at the NCover 1.5.8 release, and it *almost* includes the very feature I need to do UI testing, i.e.

"I've added a new option //pm to handle the case of .NET child processes. The problem occurs if you use NCover to launch a .NET process, which launches another .NET process. NCover previously profiled the first .NET process in the chain. However, if you had a test application written in .NET that executed a child process and you want to collect coverage data on that child process, you were out of luck. Now, with the //pm option you specify the "module" name of the process you wish to profile. The module name is the name of the process' main executable file (not including the path). If this option is used, NCover will ignore processes that do not match this executable name and it will only profile the first process with that name if there are more than one. Here is an example command line for a test where the TestLauncher application launches the MyTest process."

This is perfect except for the bit about "it will only profile the first process with that name if there are more than one." I've been writing my UI tests to start and stop the UI each time to make sure they can start from a known state. Most easily, this means stopping the UI after each test and starting it back up again on the new test. However, if NCover will only track the coverage for the "first process" specified in //pm, I'm kinda outa luck. May I suggest a //pmall option that tracks all child processes specified by //pm instead of just the first? Thanks!

Re: Coverage.xsl not being copied

I experience a similar problem. I have copied the Coverage.xsl manually, then opened Coverage.xml...and it was empty.