Living with StyleCop

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. ;-)