In Visual Studio:
In dotCover standalone application:
If you need to analyze coverage of a .NET process that is started in a custom way, you can start the Coverage Controller first, and then start your .NET process. dotCover will then attach to the process automatically and record coverage analysis while the process is executed.
To analyze coverage of an arbitrary .NET process
- Do one of the following:
In Visual Studio, press Ctrl+Alt+K K or choosefrom the main menu
In dotCover standalone application, press Ctrl+Alt+K K or choosein the menu.
In the Coverage Configuration dialog that appears, choose .NET Process.
- Optionally, select the Advanced check box to configure additional settings:
If you cannot guarantee that the covered process will be started right after you click Run, set up a process filter in Cover only specified .NET processes:
There can be only "include" masks. Therefore, any filter mask you add means "profile anything that matches this mask".
You must specify process names including the
*wildcard is supported.
For example, to run coverage analysis for all processes that end with
service, add the
Click Edit Symbol Search Policy to specify where to search for PDB information.
Click Edit Filters to view existing and add new coverage filters. Note that the filters you add with this button are only applied to the current session.
- Click Run. dotCover will open the Coverage Controller dialog and then
wait for the first .NET process that starts.
Start your .NET process.
As soon as dotCover detects the process that matches the specified filter, the controls in the Coverage Controller dialog become enabled and you can start the coverage run.
If the Collect profiling data from start check box was selected, the coverage run starts immediately. Otherwise, dotCover waits until you click Start in the Coverage Controller dialog. When the coverage run is started, you can record code coverage.