Hi,
Today I was thinking to write about some of the new features of Static Code Analysis in Visual Studio 11, but better get this post of the draft folder and make it public.
When working on a project, regardless of the tool that we use for the analysis of static code (Code Analysis, FxCop, etc.) it is always advisable to apply the following rules
- At least a minimum set of analysis rules apply to all projects. Based on the principle of "least da a stone", this helps us protect us from future mistakes. In the case of Code Analysis, the set of "Minimun Rules" is ideal.
- You have to work in a continuous integration environment, this so am assuming. In the event that the analysis process consume too much time in local, it is advisable not to perform validation of Code Analysis in local. That Yes, in the process of continuous integration is due to force static code analysis
- Fundamental. Do not ignore the Warnings in the builds, dedicate time and solve the problems detected in them. Many times I prefer to change the mode of Warning Notice error, only to force to resolve the problems detected on static code analysis.
- Finally, and optional. If someone wants to have local detail, activates the process of Code Analysis in local. Visual Studio allows you to do in 2 clicks.
Saludos @ Home
El Bruno
 |
 |
 |
References:
List of tools for static code analysis
http://en.Wikipedia.org/wiki/List_of_tools_for_static_code_analysis
El Bruno 
Leave a comment