Weird 'Line' and 'End' values

Hi

Some of the 'Line' and 'End' values are 16707566. For example, ...

Visits Line End Column End Document 1 12 12 9 101 C:\DataDefinitionContainer.cs 1 13 13 9 79 C:\DataDefinitionContainer.cs 1 16707566 16707566 0 0 C:\DataDefinitionContainer.cs

Re: NCover.Console 1.5.5 crashes when run

Sounds like a corrupted install somehow. For NCover 1.5.5 the Assembly version number of the NCover.Framework.dll should say 1.5.5.0, not 1.3.2.0.

I suggest an uninstall, make sure the directory is clean/removed and a reinstall. Check you haven't accidentally got anything installed in the GAC too. Also you could try NCover 1.5.4.

Re: NCover.Console 1.5.5 crashes when run

Thanks

Re: Installation guide

There are plenty of tutorials around if you Google it - this one by Craig Murphy is quite good:
http://www.craigmurphy.com/blog/?p=240

As an "installation" there isn't much to NCover - the only gotcha I found is that for versions later than 1.3.3 you need to install the latest Windows debugging .dlls if you are only on Win2K.

The "fun" part is getting the command line syntax correct in the likes of NAnt tasks when executing NUnit tests etc - again Google should find some examples if there aren't any already on the forum.

One point to be aware of is some of the command line parameters have changed between 1.3.3 and the latest 1.5.4 versions which can cause some confusion - it's a straightforward like for like from memory but just in case you find a web article or posting that refers to different parameters that is why...

Re: Installation guide

Thanks, just got to get it working with Nunit now for code coverage on a site and im good

Re: Installation guide

Craig's document did not explain how to use nunit with ncover. This is what I was hoping to find. Did I miss something? It was a decent beginning document on TDD for .Net.

Re: Installation guide

I see from your other post that you got NCover working with NUnit using TestDriven.Net (which is the best way to go about doing it for iteratively improving your test code). Does that answer your question or do you have something specific in mind?

The other situation (which incidentally is what TestDriven.Net does on your behalf) is when using NCover from the command line for running unit tests, such as on a build server from a NAnt script. Craig's article only shows usage of the command line for running his app prior to unit tests but the principle is exactly the same - except instead of "calc.exe" you instead run "nunit-console.exe" with the extra parameters for nunit such as which test assembly or project etc.