NCover doesn't accept parentheses in paths

NCover 1.5.8 seems to be failing when I use paths containing parentheses within its command line options. The error message reads:

X was unexpected at this time

...where X is the part of the path following the closing bracket ")".

In my case, the error occurred with the //x option, and also when I used such a path as a command line option to NUnit (I was testing test code coverage).

This did not seem to cause any problems with 1.5.4, which we were using up until now.

Re: Calling NCover from within an app?

Since it is ASP.Net, I'm not too sure this would work.

I had a situation where I could not do coverage because part of the software was calling another Exe (and THAT exe was what I wanted to cover). We used reflexion to call the Exe so then it landed in our process and not in another process.

So, depending on how you are set-up (or ASP let's you do it) maybe you can call NCover from the beginning of your software and have it execute something to hook back on your system.

Again, having doubts this will work with ASP, but if it can help to see other solutions...

nick