In Visual Studio.Net 2003, non-visual page elements (such as DataReaders, DataSets, etc.) were kept in a separate tray area, where they didn't interfere with the design-time layout of the page. However, in Whidbey, non-visual elements (such as DataSources,
WebPartManagers, etc.) are displayed on the design surface, where they interfere with the layout of other elements on the page. This makes it difficult to see at design time what the page is going to look like at run time. Are there plans to bring back the
component tray to separate non-visual elements from those that render a UI?
Why not just stick with the component tray like we have in VS.Net 2003? I like that idea better than having to hide/show non-visual elements. It just makes more sense to me to keep UI elements separate from non-UI elements.
Foretel
Member
165 Points
33 Posts
Why do non-visual elements take up space on the design surface?
Apr 04, 2004 06:55 PM|LINK
Mikhail Arkh...
All-Star
33139 Points
6083 Posts
Microsoft
Re: Why do non-visual elements take up space on the design surface?
Apr 05, 2004 03:53 AM|LINK
------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
Foretel
Member
165 Points
33 Posts
Re: Why do non-visual elements take up space on the design surface?
Apr 05, 2004 02:47 PM|LINK
davidvl2
Member
440 Points
88 Posts
Re: Why do non-visual elements take up space on the design surface?
Apr 05, 2004 06:47 PM|LINK