Master Pages

[Steve]

Playing around with Master Pages for the first time and wanted to get
thoughts on the best way to use them.

Do most developers use a different Master Page for each section and then
combine the Pages together on the .aspx pages? Or do they use one primary
Master Page that has a table with different rows/columns/cells that have
their own content controls. If they combine them, how do they set the .aspx
page to use multiple masters?

Thanks

Steve

 

[Mark Rae]

Do most developers use a different Master Page for each section

"for each section"...?

What sections are you talking about...?

 

[Steve]

Header, Footer, Left Column, Center Column, Right Column, etc.

 

[Mark Rae]

Header, Footer, Left Column, Center Column, Right Column, etc.

Ah right - you appear to be confusing MasterPages with framesets...

 

[Steve]

What I've done is create a masterpage. Added a table to it. And then in
certain cells of the table, have content frames for header, footer, menu
bar, center content, left content (like for tree), and right cell content.
What I wanted to know is this method a standard in the industry or do most
developers use seperate master pages for each cell. I'm not familiiar with
framesets yet.

 

[Mark Rae]

What I've done is create a masterpage. Added a table to it. And then in
certain cells of the table, have content frames for header, footer, menu
bar, center content, left content (like for tree), and right cell content.
What I wanted to know is this method a standard in the industry or do most
developers use seperate master pages for each cell. I'm not familiiar
with
framesets yet.

Slightly confused... You say you're not familiar with framesets, but you
have "content frames" in your table - are these iframes, then...?

It might be easier if you post your MasterPage's markup...

 

[clintonG]

Briefly, MasterPages can be thought of as templates that can contain content
that is static or generated dynamically. The notions of a header used
primarily for navigation, a body used primarily for content and a footer
used primarily for copyright and related links to privacy policy for example
are the three basic page "zones" noting to the best of my knowledge we
really haven't reached a general consensus to standardize what we call the
areas of a page other than to refer to them as the header and so on or a
zone or some other analogy like a frame. Maybe that's where Mark is coming
from using the analogy of an HTML Frameset.

The "best way to use them" (MasterPages) is for the most part strictly
subjective from a design perspective and there's lots to learn. Go to K.
Scott Allens' website [1] as he has the most comprehensive blogging and
tutorials I believe. Secondly use Google's site: filter to search for
specific documentation from msdn2 where the latest ASP.NET 2.0 documentation
is.

// example
Master Pages site:msdn2.microsoft.com

--
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
MAP http://wikimapia.org/#y=43038073&x=-88043838&z=17&l=0&m=h

[1] http://odetocode.com/