I’ve been trying an experiment - having integrated StyleCop into my build scripts (using StyleCop.cmd), I’ve been working to reduce the number of violation messages that it reports.

The key is that I haven’t spent very much time making changes just to keep StyleCop happy - rather, I’ve been continuing development as normal, writing code, fixing bugs and so on, but with half an eye on StyleCop’s metrics.

In effect, I’ve been letting StyleCop train me into a few new habits, habits that I believe improve the maintainability (long term viability) of my code.

Increasingly, I’m finding that my new code has few (if any) new issues reported by StyleCop, with negligable overhead.

I guess this is similar to the way that the C# compiler has trained me to write code that is warning free. Perhaps I should roll FxCop into the mix as well. ;-)


blog comments powered by Disqus
Next Post
StyleCop Cmd Updated  27 Jul 2008
Prior Post
Intersect and Except  24 Jul 2008
Related Posts
New Release of StyleCop Cmd  19 Sep 2010
Why use StyleCop?  01 Aug 2008
Stylecop Documentation and Supression  01 Aug 2008
StyleCop Cmd Updated  27 Jul 2008
Announcing StyleCop.cmd  01 Jul 2008
More on StyleCop  30 Jun 2008
StyleCop for C# Coding Standards  28 Jun 2008
July 2008