How do you feel about code folding? [closed]

Answer 1

While I understand the problem that Jeff, et. al. have with regions, what I don't understand is why hitting CTRL+M,CTRL+L to expand all regions in a file is so difficult to deal with.

Answer 2

My approach is similar to a few others here, using regions to organize code blocks into constructors, properties, events, etc.

There's an excellent set of VS.NET macros by Roland Weigelt available from his blog entry, Better Keyboard Support for #region ... #endregion. I've been using these for years, mapping ctrl+. to collapse the current region and ctrl++ to expand it. Find that it works a lot better that the default VS.NET functionality which folds/unfolds everything.

Answer 3

The Coding Horror article actual got me thinking about this as well.

Generally, I large classes I will put a region around the member variables, constants, and properties to reduce the amount of text I have to scroll through and leave everything else outside of a region. On forms I will generally group things into "member variables, constants, and properties", form functions, and event handlers. Once again, this is more so I don't have to scroll through a lot of text when I just want to review some event handlers.

Answer 4

Sometimes you might find yourself working on a team where #regions are encouraged or required. If you're like me and you can't stand messing around with folded code you can turn off outlining for C#:

1. Options -> Text Editor -> C# -> Advanced Tab
2. Uncheck "Enter outlining mode when files open"

Answer 5

I personally use #Regions all the time. I find that it helps me to keep things like properties, declarations, etc separated from each other.

This is probably a good answer, too!

Coding Horror

Edit: Dang, Pat beat me to this!

Answer 6

I really don't have a problem with using #region to organize code. Personally, I'll usually setup different regions for things like properties, event handlers, and public/private methods.