Old defect in 1.3.3 - is there a workaround?

We don't/can't use the 2.0 framework at work, so I'm stuck with 1.3.3. I seem to be running into this problem:

http://www.ncover.org/COMMUNITY/ShowPost.aspx?PostID=33

A fix for which went into 1.4.5a according to the post.

Is there a chance of making the source of 1.3.3 available so that we might take a crack making the mentioned fix ourselves?

Thanks.

Re: NCover commandline call from Nant Script

The NCover NAnt/MSBuild tasks are something I put together in assemblies that you need to download from my website. You will find them in the NCoverExplorer.Extras.zip file on the download page here:

http://www.kiwidude.com/dotnet/DownloadPage.html

The documentation with examples are both included in the zip and available on my site.

Re: NCover commandline call from Nant Script

hi, thansk for the reply

I have already looked into the extras zip file, but it contains many tasks i dont really need. (msbuild etc.) and i also have a custom versioning label system that i want to keep.

I just need to see where my syntax fails in the above if anyone can help

thanks

Re: NCover commandline call from Nant Script

Not quite sure what you mean about your versioning label system etc - the dlls contain just optional tasks you can include in your script. How many of their tasks you use is entirely up to you but certainly you can just ue the <ncover> task if that is all you want out of it without impacting anything else.

You are using the wrong command line syntax if you want to stick with the exec task. You are using NCover 1.5.4, which uses the // syntax for its command line arguments.

You can use the NCoverExplorer gui to generate the NAnt task for you in the run NCover dialog. If you want the <exec> task just untick the "Use custom <NCover> tasks rather than <Exec>" option on the NCover tab.