After maintaining lots of code littered with #region (in both C# and VB.NET), it seems to me that this construct is just a bunch of \"make work\" for the programmer. It\'s w
Like any language feature, regions have the potential to be misused and abused but they also have their benefits.
They are great for creating "folding" groups around:
You can also use it to group properties, public/private methods, events, class-wide variables, etc.
I use regions in my code to help create a consistent structure in my code so I always know where things are at a glance. Yes, it makes things a bit harder during refactoring or adding new functions (especially when autogenerated by Visual Studio) but I feel it's a small price to pay to keep things consistent and structured.