Most people think that the previous behavior was a bug, not a feature,
because whenever you did that you 'lost your place' in the code you were
working in. A workaround for that problem was to place a bookmark before
moving the splitter, and to then navigate back to the bookmark to get back
to wherever you were before you did the split. A rather irritating sequence
of actions to have to go through to merely split the code window so that you
could look at something else of interest.

The C# code editor didn't have that bug, and personally I'm glad that it's
finally fixed for VB.Net in VS2005.

But if you don't agree with me about that, you may also not agree with me
that enclosing each individual member in its own region is an excessive use
of the Region feature. The intent of the Region feature is to group similar
pieces of code - for instance, all the constructors, all the instance data
members, all the private members, etc. Or any other sort of grouping that
appeals to you. For instance, you might group all the event handlers that
belong to context menus. That, for example, is how the IDE used it for
Windows Forms in VS2002 and VS2003, so that all the IDE-generated code would
be in one place, normally collapsed, and would not clutter up the editor's
view of the file.

Tom Dacon
Dacon Software Consulting