…

@LosManos - For these GUI classes I like MVP. In the view I too like the “WireHandlers” (or similar) method. I use anonymous delegates where possible that generally call right back into the Presenter. Easy to read.

I don’t get you how rip regions but say: “Just stack them in order and you won’t need regions. Put things in plain view!” sounds like you’re contradicting yourself!

Most classes are small, but some are big, that’s life. Sometimes a module is… a module.

Especially working close to the user interface classes tend to get big. At least one method per user action, and user actions are plenty in a GUI.

During my years pretending to work I haved found out that a “form class” contains several parts where one is the event sink where all events from the surrounding world is caught. This region I call “Event handlers” or “Event sinks”.
( Yes, I have names for the others to but that is out of scope. )

I have two solutions (besides inventing some fancy class relation-inheritance-interface-composition-pattern structure)
1) divide the class into files with “partial class”
2) use regions

Both ways work good.

/OF

this OO thing is overrated as well :)

I find that the motivations behind heavy usage of regions can generally be satisfied with other tools such as Resharper. If you consistently use something like Resharper 3’s Format Code to keep all of your classes consistently formatted that, in combination with smart Go to Declaration and Incremental Search should be all you need.

Regions strike me as a hold-over VBism, which is probably why they are so popular.

All specifics aside when I’m finding code 9/10 times it’s to try to grok what someone else wrote. If there’s a BDD-style test this is the best way, by far, for me to see the pieces. If not, well why not?! Okay, accepting there isn’t a nice, expressive test my heuristic then takes me to looking at class names or a pointer from the author (if available). At that point, 95% of classes should be so small as to not need regions.

I would have to disagree with you 100% on this one. Epically #4.

I believe that regions are great, they allow me to be more productive and find code much easier, faster.

If i know a method is private, why filter through all the public ones to find it. Simply expand the private region and i have what i want.

Derik

Definitely gotta get together soon. It’s been an unusually busy summer.

Fields, Constructors, Type specific (meaning to the class/interface) methods, Type specific properties, Interface implementations, Helper methods, Nested Types.

Later,
Drew

P.S. We gotta grab some Lombardi’s again soon! ;)