Implementing a code analysis tool for Visual Studio 2010

Abstract

Code analysis is a very important issue nowadays. In late 80s people only tended to try to make their software qualitative. Nowadays it is a must for a professional software developer and is one of those critical criteria which separate the best from the rest. Code quality is a scientifically studied question with a big enterprise background today bringing such massive systems as NDepend or FxCop to the community table. These giants are really difficult to fight against because of their achievements but their products have their slight shortcomings too. These disadvantages can be their nonlinear curve of mastering them, their language which is far from being ubiquitous [1], the high price in the case on NDepend. There is also one more peculiarity which walks along the above mentioned: quality is a perceptual, conditional and somewhat subjective attribute and may be understood differently by different people. Anyhow we insist that there are some commonly recognized criteria for detecting bad code but that does not mean that one cannot think of his own ones. The described system tackles all these issues.