Support
CONTENTS
Automating NCover Registration
Batch Script for Simultaneous Coverage
Coverage Data Inconsistencies in NCover 3.0.22 and Earlier
Displaying NCover Results in Bamboo
Duplicate Assemblies in Merged Coverage File
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
There are a few cases in which the NCover environment does not get reset after running NCover on services or IIS.
Symptoms
An NCover environment that has not been properly cleaned up will cause every .NET application to take an abnormally long time to load. This time is caused by NCover being loaded by the application and proceeding to attempt its handshake with NCover.Console.
Causes
This scenario is primarily caused by NCover being killed during execution. This is especially common in build server environments where the build server includes functionality to stop the build.
Solution
The environment variables that cause this issue to occur are set in the registry. Open regedit.exe and browse to HKEYLOCALMACHINE\System\CurrentControlSet\Control\Session Manager\Environment and delete the following keys:
- CorEnableProfiling
- Cor_Profiler
- NCover_PID
