NCover Documentation

We are pleased to announce that v3.0.18 of NCover is officially released. The biggest change is in the handling of source files that belong to multiple assemblies. How does this happen? One way this can happen is if you have "myassembly" v1.0.1 and "myassembly" v1.0.2 in your coverage file. Unless you branched your code, the source file's path will be the same. Another way this will happen is if you "Link" your source files into multiple projects. We are telling you about this change in case you are post processing the file and expect the url to be unique. Old coverage and trend files will continue to work in NCover Explorer and NCover Reporting.

Features and Improvements

  • Documents are now per module. This will allow you to obtain coverage for multiple versions of the same assembly and for linked source files
  • 30% increase in performance for merges that contain many filters

Bug Fixes

  • It was possible to open a recent coverage or project file while NCover was running
  • Fixed issue with Typemock Integration
  • Fixed issues with TD.NET Integration. v2.19+ of TD.NET is required
  • Fixed issue with NDepend v2.11.2 reading NCover 3 coverage files
  • Merging wasn't keeping the source filters from the original/first view
  • Statistics for nested classes are now calculated correctly in the reports and tree view control
  • The registration program now launches after the install is complete
  • The 32 bit installer will now install without registration problems on 64 bit systems


  • We no longer show 100% covered for items with no points in the stats pane. It is now displayed as N/A
  • Fixed localization issues with the Cyclomatic Complexity statistic in trend and coverage files by changing the field separator to a semi-colon (it was a comma)
  • Documents are now per module which means their URL may be duplicated in the coverage and trend file (but they're still unique by ID, and are unique by URL and module ID as well)
  • Coverage for a single assembly is now merged across all application domains it was loaded into, which gives a more accurate coverage statistic. Before, coverage for the assembly was reported once per application domain it was loaded into, giving multiple instances of the same assembly in the coverage data, some with really low coverage and some with really high coverage
  • When NCover is running, only the "Output View" and "Trend Pane" buttons and the help tab are enabled
  • The Registration program no longer requires administrative credentials in order to run
  • CC.NET reports incorrectly displayed the acceptable coverage threshold for methods.
  • Branch Point coverage thresholds were not correctly supported in NCover Reporting

If you still need technical assistance, we can help:

Submit A Support Ticket