Microsoft released the internal tool StyleCop to public under the fancy yet boring name of Microsoft Source Analysis for C#. Even though the name is boring the product is not.
You'll love this tool when it imposes consistent coding style across your team. You'll hate this tool when it imposes the same on you. The result is stunning looking, consistently styled code which your whole team can follow uniformly.
StyleCop has been in use for a long time internally in Microsoft and many teams mandate it's usage. My previous team VSTT used it as well. The only crib I had is that it didn't allow single line getters and setters (and our team didn't agree to disable this rule either).
// StyleCop didn't like this one
public int Foo
{
get { return Foo; }
}
// StyleCop wanted this instead
public int Foo
{
get
{
return Foo;
}
}
Read more about using StyleCop here. You can set this up to be run as a part of your build process as documented here. Since this is plugged in as a MsBuild project you can use it in as a part of Team Foundation Build process as well.
Let the style wars begin in team meetings :)
2 comments:
I recently developed a command line interface and NAnt task for StyleCop as well called StyleCopCmd at http://stylecopcmd.sourceforge.net/.
I am reading this article second time today, you have to be more careful with content leakers. If I will fount it again I will send you a link
Post a Comment