As you privided in your comment, you said the problem got resolved after changing the Actions from CriticalWarning
to Warning
, and CriticalError
to Error
.
This behaviour is explained here: http://msdn.microsoft.com/en-us/library/dd380626.aspx
You must have mistaken the action for the MessageLevel property
in custom rules XML-files. In this property you can set the following values:
- Critical Error – Issues reported with this level have high visibility and the identified code does not operate correctly in most common scenarios. These issues should be resolved first. You should not exclude issues with this level.
- Error – Issues at this level have less visibility and impact. But it still identifies issues in your code you need to resolve. Also these issues should not be excluded without careful consideration.
- Critical Warning – This level is mostly used for maintainability issues of your code. The code is working correctly but less-than-optimal. Exclude such messages only after careful consideration.
- Warning – Messages with this level are identifying issues in your code around maintainability, extensibility and stability.
- Informational – Informational messages about the code.