You can resize the ContentPlaceHolder if you want but the virtual space it
infers when viewed in the designer becomes meaningless at runtime. When
you're working in the designer its like an allusion you have to get used to
noting the Visual Studio designer is worse than FrontPage ever was. Its
especially crippled when working with MasterPages. In this context Visual
Studio will likely remain crippleware for a long time to come. I work in
source mode and miss the efficiency that has been promised.
What's even worse is FrontPage has been redeployed for use with SharePoint
and a "new and improved" application called Microsoft Expression Web is in
development. At face value its an outstanding choice for the design phase of
a project but it too is crippleware and can not really be used with Visual
Studio in any way I could consider credible. Maybe I missed the button that
says "Export to Visual Studio?"
The question on my mind is wondering if Ray Ozzie will make quality a
priority.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL
http://clintongallagher.metromilwaukee.com/
MAP 43°2'17"N 88°2'37"W : 43°2'17"N 88°2'37"W
"Bob" <ms****@hotmail.comwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...
>I want to use a master page so that all my pages have the same look but it
seems odd that once you create a master page you only have a little content
window to work in for the rest of the pages. Since the content object is
not resizable this makes designing the content pages very difficult. May
be I am missing something. Is there a better way to do this?
Bob
