Once you get used to VS.NET, it is not that important. WIth VS.NET, you have
the ability to hide the implementation of procedures when you are not
working on them, leaving only the one you are working on open. While it may
seem like a step back, it is actually quite useful, once you get used to it.
You can also group items, using #region and #endregion tags. Now that I am
used to VS.NET, I would not want to go back, personally. You may feel
differently.
BTW, the help file explains Microsoft's take on this. Lookup the topic:
PRB: Procedure View Is Not Available in Visual Basic .NET Project
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************** ********************
Think Outside the Box!
************************************************** ********************
"Yaris" <ag********@hotmail.com> wrote in message
news:c6**************************@posting.google.c om...
Does anybody know if we will see the very usefull Procedure View
feature in VB .NET? As a VB veteran it is really annoying me not
having the features which previously made VB my language of choise. As
often with MS it is two steps forward and one - or maybe - one and a
half step backward.
