The Code Central user guide isn't intended to be a complete list of all the possible scenarios for collecting coverage data. However, if you understand how code coverage works, you can apply this principle to any project.
NCover 4 runs as a service, which means it's always monitoring and ready to cover any .NET code executing on your machine. This ability to gather data globally is key to understanding how to leverage the power of NCover 4.
Code Central can profile processes running locally, or receive coverage data from a connected instance of Collector running on a local machine and sending the data back to Code Central automatically.
All Projects are created and configured in Code Central, then synced to Collector in a read-only view.
When setting up any project, the first question you should ask is What process do I want Collector to cover?
If you can answer this question in the form of a match rule that tells Collector how to find the executable or service that's exercising your source code, you can collect detailed coverage data and metrics.
The coverage scenarios in this section will guide you with examples of how to profile your tested code in a variety of environments.