Improve the source zip

Hi,

A couple of times I have downloaded the source intending to locate and fix a particular bug that is holding back my project. However, both times I have been discouraged by the fact that necessary headers and what-not are missing from the source (eg. boost headers).

Is there any chance these dependencies can be included in the source download so I can just download, build and get debugging? Myself and other developers wouldn't have a clue what version of boost is being used, which makes it kinda hard . . .

The way I normally tackle this is to include a Lib or BuildLib directory in the source tree and put all dependencies in there. Then my projects will reference those dependencies and the source download will include them.

Thanks,
K

Re: Improve the source zip

The boost headers can be downloaded from http://boost.org. ; I think those are the only headers missing from the source distribution.

Re: System.BadImageFormatException : An attempt was made to load

That's correct. NCover will not generate coverage for dlls that don't have pdb's. Can you upgrade to NCover v1.5.4? I don't think you will experience this issue with the new version.

Re: System.BadImageFormatException : An attempt was made to load

I'll try again,
but I thought v1.5.4 depends on .Net 2.0,
and this is a .Net 1.1 program.

Is there a way to include the .Net 2.0 needed assemblies into the same folder as NCover?
--> I can not install .Net 2.0 on the development machine, company policy

Can I recompile NCover into .Net 1.1?
Are there really .Net 2.0 specific assemblies needed?

with kind regards

Re: System.BadImageFormatException : An attempt was made to load

That's true, 1.5.x depends on .NET 2.0 at this time.

Re: System.BadImageFormatException : An attempt was made to load

Hi

I tried to recompile, but there are 2 .Net 2.0 specific assemblies referenced,
which makes it impossible to easily convert it to .Net 1.1

So therefor, is it possible to include these assemblies in the distribution?
add the needed .Net 2.0 assemblies in the same folder as the others?

with kind regards

Re: System.BadImageFormatException : An attempt was made to load

It is not possible to include these assemblies. Licensing issues aside, the .NET framework is not supported as a partial installation. You really have to install the entire thing to get that functionality.

Re: System.BadImageFormatException : An attempt was made to load

Hi

I got the .Net 2.0 issue solved, so NCover 1.5.4.0 is working.
System.BadImageFormatException is not gone however

Is this a bug in NCover, or in NUnit?
How can this be solved?

I mean :
- running Nunit on its own works
- running NCover on other assemblies works
- running NUnit in NCover, where an assembly does something with interop :
BadImageFormatException

Is there a way to get more information?

Re: System.BadImageFormatException : An attempt was made to load

How did you fix the 2.0 issue? Did you get .Net 2.0 installed on your machine?

I need to get more information on how the error is produced. Can you send me a snippet of code that reproduces the problem?

Re: System.BadImageFormatException : An attempt was made to load

Hi

Virtual PC is nice ;-)

I found the reason : security !
The exact reason is still not known, but the code was located on a file share.

I was trying to duplicate the error, in a small application, and made this on my C Drive.
No error on the simple functions, than the ones with failing unit tests, still not a problem.
Afterwards I double checked that the referenced dll's where the same, and that the version
of Nunit and NCover where the same. All ok.

So the only difference was the location of the files, and after copying my test program to
the fileshare, it also failed. Copying my first program to my c drive resolved the issues.

I will try again with NCover 1.3.3 tomorrow, and let you know if it also works with this version.
If so, this would be excellent !

damn security ;-)

regards

Re: System.BadImageFormatException : An attempt was made to load

I tried again with NCover 1.3.3, and it works.

So for summarizing :
- ran it on my C drive (security related, what I do not know)
- use NUnit 2.2.7 (Nunit 2.2.0.0 did not work)

So for people with .Net 1.1, you know what to do ... ;-)

Re: System.BadImageFormatException : An attempt was made to load

The 1.1 and 2.0 runtimes have separate settings for security, so maybe you have 1.1 configured to allow execution from remote drives, and 2.0 configured otherwise, and that's causing the problems.

The default settings don't allow full access to programs running on network shares.

Re: System.BadImageFormatException : An attempt was made to load

Hi
below is the security setting for the file share, as it always was.
I just renamed the actual machine name and the share name.
Looks good to me.
----------------------------------------
LocalIntranet_Zone Code Group

Description:
All code from this directory will be trusted.

Assembly evidence must match this membership condition to belong to the code group:
Url: file://<Machine_Name/<Share_Name>/*.

Assemblies matching the membership condition are granted this permission set at the current policy level: FullTrust.

Permission Set Description:
Allows full access to all resources

Re: mock object coverage

I should have read the blog first!

http://ncover.org/SITE/blogs/ncover_blog/archive/2006/01/29/103.aspx

Sorry.

Re: setting coverage and threshold for ncover from NCover consol

NCover itself has no concept of coverage thresholds - or indeed coverage percentages for that matter. It just produces a raw xml file which can be transformed to give percentage information.

NCoverExplorer is the tool to use to manipulate the coverage.xml file produced by your command above to make use of concepts such as coverage thresholds. If you look back through my blog or in the sample files in the NCoverExplorer.Extras.zip also available for download from my site you will find examples of using this. You can either configure a threshold in the GUI for when you are interactively examining the coverage information, or on the console application command line to use for reporting purposes and/or to fail continuous builds if thresholds are not met.

Re: NCoverExplorer Report on CCNet Incorrect when Excluding Asse

Montana,

As per my reply to your other post my apologies for the delay in missing this post. I've been snowed at work the last few weeks and not properly looking at the forums. If I see a new post on the summary page I respond to that but I dont always remember to drill into the forum itself to see if there were other posts.

My first question would be why are you coverage profiling nunit as well as your application anyway? Remove the .pdbs from your nunit bin folder and NUnit stuff will no longer appear in the coverage.xml file, so you dont need to do any exclusions yourself. That should result in the numbers coming right.

As for the totals being incorrect, that's rather interesting. I will log it as a bug and take a look when I get back to NCoverExplorer again in a week or so. Thanks for bringing this up.

Re: NCoverExplorer Report on CCNet Incorrect when Excluding Asse

Montana,

It's taken longer than I had hoped but I've finally had some "NCoverExplorer" time again to fix various bugs etc. Amongst them I have done a lot of work on the merging of NCover files which had numerous issues due to the problems of noops and different scenarios when NCover removed them with differing versions.

Anyways if you would be so kind as to try the latest version from the link below and tell me if you are still experiencing the issues you noted previously with the coverage totals.
http://www.kiwidude.com/dotnet/NCoverExplorer_1.3.6.zip

Re: Command line report generation?

Hi Jason,

Absolutely you can do it from a command line. There are NAnt and MSBuild tasks to do this in the NCoverExplorer.Extras.zip on my download page, or you can just run the ncoverexplorer.console.exe directly. If you run it with no arguments (assuming you are using one of the latest versions such as 1.3.6.x) then you will see a bunch of examples and the syntax.

The commandline if not using NAnt/MSBuild would be something like:
ncoverexplorer.console coverage.xml /h:MyCoverage.html /r:3

with other options available to specify sorting, filtering, project name etc.