Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When using Code Analysis and Code Contracts in combination, I get a lot of warnings like
CA1062: Microsoft.Design : In externally visible method ‘Foo.Bar(Log)’, validate parameter ‘log’ before using it.
In Foo.Bar, I have a contract that validates log.
public Bar(Log log)
{
Contract.Requires(log != null);
log.Lines.Add(...);
// ...
}
Is there a way to make FxCop understand code contracts?
No I do not think it’s possible in the current build as the code generated by the contracts rewriter does not produce the standard pattern that FxCop is looking for.
Typically though I disable this particular FxCop rule when using code contracts. I find the static verifier more than makes up for the loss of this rule as it will yell about a lack of checking much more aggressively than FxCop. I would suggest the same approach here which will fix this problem for you.