#1 Attribute-based rules

[Dan Ports]

The attached patch allows you to include or exclude classes from the coverage report based on attributes. Attribute rules are of the form attribute:<<type>> where <<type>> is the full name of the attribute class you want to match. For example, the following rule would exclude any classes with the CompilerGeneratedAttribute from the report:

PartCover.exe ... --exclude=attribute:System.Runtime.CompilerServices.CompilerGeneratedAttribute

Or, to include classes with the ControllerAttribute:

PartCover.exe ... --include=attribute:ControllerAttribute

Please excuse my rusty C++... :)

[Dan Ports]

Patch for r4

[Shaun Wilde]

Useful idea - this patch is quite hold so not sure how well it would apply however I can see why you may need it especially for classes/methods for which you wish to ignore coverage (e.g. Mock objects etc)

Thanks