Several years ago I had gone so far as to write a VS macro to help my team and I keep a large C# codebase “clean” (members grouped in regions, sorted, etc.). For something that had just been thrown together in my spare time, it seemed to have a very positive impact on our productivity. However, after moving on to a different project, I soon realized that my macro would need a lot of work to match the style conventions of any other team.

Thus, I set out to create a tool that was configurable and didn’t rely on the Visual Studio FileCodeModel. I’ve never used ReSharper or it’s Type Members Layout feature, but believe my tool is very similar in concept (i.e. uses an XML configuration to define the code layout).

NArrange is open source and you can check it out at: http://narrange.sourceforge.net

Looking forward to any feedback…

http://idesign.net/idesign/download/IDesign%20CSharp%20Coding%20Standard.zip

I call.

Oh, and I dropped the “_”‘s from my private variables over a year ago. With tools like R# that can color code your private variables different from method parameters and local variables, I don’t really see the need in using the extra noise of underscores. But of course, like most things, it’s all about personal/team preference.

Bottom line, before I had ReSharper I was absolutely obsessed with keeping my code perfectly organized, but now it “just happens” for me, leaving me to worry about more important things.

Thank you JetBrains!!!

(I’ll up the ante and say that’s my .10)

“…and seeing reams of code is a surefire way to make me dismay.”

Jason eluded that regions tend to hide technical dept. This is occurring because of low cohesion and solubility. This is a code smell.

Look for orthogonal constructs within the object where behavior can be refactored into other objects. The will lead to a more supple design.

my two cents. OK maybe a nickel.

ReSharper is your friend.

I personally don’t like regions, if you have to use them, your class is probably doing too much. To avoid a backlash though, it depends (aha…my Ocampo moment) on what the team decides on.

I could code with my variables going backwards, just as long as their are standards agreed upon by the team.

Excellent first post Colin.

I know what you mean about being very peticular about how the code is arranged in the files.

A couple of things I follow in my own coding styles are:
- Underscores like you mentioned for class level private variables
- Camel casing on private fields, Pascal casing on public fields
- Private fields go at the top, followed by ctors, then properties and finally methods
- All brackets are on their own line
- using statements at the very top of the file outside the classes namespace decleration

thats all I can think of off the top of my head.

good post! I think it aspires to each of us