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.
What are the basic minimum set of Code Analysis rules that you would recommend for a 200K LOC solution? We’re using unit testing but code analysis has been turned off.
Ideally all rules would be turned on by default but I’d like to do this gently and turn on rules in batches so we do not have to deal with everything at once. So, what rules do I start with?
I’ve found a list of rules turned on by Microsoft as of 2007.
Not really a set of rules but a good advice on turning on Code Analysis on an existing code base can be found in Phil Haack’s answer to a related question.