Weird results with classes using generics

Hi

When running ncover against classes that utilize generics, the code coverage results vary between different machines. I can't really provide more information since the problem is intermittent.

Re: Failed to load symbols for module Ncover log report

NCover needs two things I am aware of to ensure you get coverage results:

(1) A .pdb file for each assembly you wish to profile.

(2) That assembly has to be loaded into memory.

So if you have combinations of unit tests that only hit certain assemblies and not others then you would get assembly results "appearing and disappearing".

Not sure if that helps explain things or if you have found a quirk... if not the what version of NCover are you using and how areyou running it?