Visual Studio Regions are like icebergs.

You never know what lies beneath. Two great hotkeys in Visual Studio are [Ctrl-M-O] and [Ctrl-M-P]. The "O" one collapses your current definitions down to outlines. The "P" one expands all outlined definitions. The great thing about that is that you can quickly get a feel for

a) the properties, events, and methods of the class and b) the complexity of the class. When you use regions, you lose both capabilities.

Here is an example of collapsed definitions without regions:

 

And here is an example with some common regions:

 

 

No sir. I don't like 'em.

Comments

[Christopher St. John]

Icebergs, huh? I was thinking maybe something different, something... chocolate covered :-)

[TheCPUWizard]

Actually I find regions extremely useful. I regularly collapse various regions while keeping other open, or collapse all of the items within a region to just the declarations. Just because a tool allows you to "mis-use" it, does not make it a poor tool. I typically use some "well defined" region names, and have a set of add-ins that will collapse all open documents completely and then just expand the regions with the desired name. Very handy....

[Russ McClelland]

Really Jef!? I love regions! They remind me so much of protocols in VisualWorks for organizing methods. We keep a few standard regions that we blow out with a CLASS macro. Some things you rarely use on a frequent basis: Constants, Construction & Finalization, Data Elements. The other things are in regions that we use all the time.

[Warc]

I disagree. Regions help you quickly browse a class and find the method you want.