Coverage exclusions to apply, in one of two formats: They can be semi-colon delimited "Type=Pattern" pairs, e.g. "Assembly=*.Tests;Class=My.*". Alternatively they can be defined in a property group as a <CoverageExclusions> section. See the examples for both formats. If you want to use regular expressions then you must use the <PropertyGroup> approach.
This example shows a range of coverage exclusions using the <PropertyGroup> approach. Note the optional use of wildcard characters in the pattern. You could set the exclusions up within the gui and then paste the xml directly from the NCoverExplorer.config file located in C:\Documents and Settings\user\Application Data\Gnoso\NCoverExplorer\
<PropertyGroup>
<CoverageExclusions>
<CoverageExclusion>
<ExclusionType>Assembly</ExclusionType>
<Pattern>*.Tests</Pattern>
</CoverageExclusion>
<CoverageExclusion>
<ExclusionType>Namespace</ExclusionType>
<Pattern>MyNamespace.*</Pattern>
</CoverageExclusion>
<CoverageExclusion>
<ExclusionType>Class</ExclusionType>
<Pattern>MyNamespace.MyClass</Pattern>
</CoverageExclusion>
<CoverageExclusion>
<ExclusionType>Method</ExclusionType>
<Pattern>MyNamespace.MyClass.MyMethod</Pattern>
</CoverageExclusion>
<CoverageExclusion>
<ExclusionType>Namespace</ExclusionType>
<Pattern>MyApp\.(\w*\.)?</Pattern>
<IsRegex>true</IsRegex>
</CoverageExclusion>
</CoverageExclusions>
</PropertyGroup>
<NCoverExplorer ...
Exclusions="$(CoverageExclusions)"
...
/>
This example shows inlining of three of the same exclusions above. Note with this approach it is not possible to use regular expressions.
<NCoverExplorer ...
Exclusions="Assembly=*.Tests;Namespace=MyNamespace.*;Class=MyNamespace.MyClass"
...
/>
NCoverExplorer Class | NCoverExplorer.MSBuildTasks Namespace