A while ago I talked about a new tool from Microsoft called StyleCop. Since then, there was a lot of confusion surrounding the tool and it has undergone a lot of changes both internally and externally.
Both Jason and Brian do an excellent job explaining the context behind some of the discussions and decisions leading up to these changes, but the biggest one is that the tool has been officially renamed as “StyleCop” to prevent any confusion with the built-in Visual Studio Code Analysis packages.
I’m not sure I agree 100% with the reasoning behind the name reversion, but I’m glad it went back to the StyleCop name. As I mentioned, Microsoft needs to choose one umbrella name for both FxCop and StyleCop as the name for the overall technology/process concept. The industry term (at least the one I’m familiar with) for the type of activities/analysis both of these tools perform is generally called “Code Analysis”. Call it that as a technology “suite” that has two tools: FxCop for static analysis and StyleCop for source code style analysis.
I’m happy to say that the newest release of StyleCop shows the direction StyleCop seems to be heading…and it’s a good direction. The new release includes various bug fixes and better Visual Studio integration, new rules documentation (which is also integrated into Visual Studio) and new rules. See Jason’s post for the full list of rules added.
A StyleCop SDK is also undergoing final review which will allow custom rules to be created, similar to FxCop.