SA1201: ElementsMustAppearInTheCorrectOrder - Statics first option

Aug 30, 2010 at 12:27 AM

I've always been putting all static members to the top of a class. Inside the static area, the correct order Fields - Constructor - Methods can of course be enforced too. But having to put a _static_ method after an _instance_ constructor just makes no sense to me. That is semantically just plain wrong. I remember in the good old Smalltalk programming systems of yore (those were rich IDEs), all static members came first too.


In my most humble opinion, StyleCop (and the rest of the world) should at least tolerate, or even better enforce that in the future.


Sure we can configure things, but the default StyleCop settings are becoming more and more a de-facto standard.