Support
CONTENTS
All .NET Applications On My System Attempt To Load NCover
Automating NCover Registration
Batch Script for Simultaneous Coverage
Coverage Data Inconsistencies in NCover 3.0.22 and Earlier
Displaying NCover Results in Bamboo
Duplicate Elements in NCover 3 Merged Coverage
Errors When Using NCover.Reporting Under The Local System Account
How are Coverage Metrics calculated?
How do pre-coverage includes and excludes work?
How to Disable Runtime Intelligence in NCover 3.0.20+
How to merge several coverage files together
How to migrate an NCover 2.1 MSBuild task to NCover 3.0
How to migrate an NCover 2.1 NAnt build task to NCover 3.0
How to track down 'Failed to CoCreate Profiler'
NCover 3 with Admin Priviliges in Windows 7
NCover Trend and Report File Definition
Handling 'No data was collected' Errors
Release Notes: NCover 3.0.5 Beta
Release Notes: NCover 3.0.6 Beta
Release Notes: NCover 3.0.8 Beta
Release Notes: NCover 3.0 Beta
Release Notes: NCover v3.0.9 Beta
Reports Available In NCover Classic and NCover Complete
Saving and Using NCover Configuration Files
Visual Studio 2008 SP1 Hangs When MSBuild Integration Is Used
This problem occurs when coverage of the same code from separate builds is merged. Multiple coverage files of identical code, when merged, will show duplicate assemblies if the build is not the same in each coverage file.
The underlying issue is the doc IDs, which are assigned when the build takes place and used by NCover to identify all the code elements. The doc IDs are different in every build -- even for the same code -- so assemblies that appear otherwise identical are still different to the NCover profiler.
