Master Pages in ASP.NETby Jesse Liberty
On many web sites, it is important to achieve a consistent "look and feel" as the user moves from page to page. While this was possible with .NET 1.1, it was difficult and required both programmer and designer discipline. ASP.NET 2.0 makes this far easier with the creation of master pages.
A master page provides shared HTML, controls, and code that can be used as a template for all of the pages of a site. Thus, you might create a master page that has a logo (e.g., the O'Reilly tarsier) and an image (e.g., the O'Reilly header) and share these images on multiple pages, as shown in Figure 1:
Figure 1. Consistent look and feel
Here's how you do it. First, begin by creating a new Web Site (Call it "MasterPages"). Right-click on your project and choose Add New Item. From the Add New Item dialog, choose Master Page, and name your master page "TopMasterPage." as shown in Figure 2.
Figure 2. New master page object
Note: The names of your project, master pages, and other pages in this example can be anything you want.
You'll note that your new master page has been created with an
asp:contentplaceholder control already in place. It is this placeholder that will be
filled by the content of the pages that use this master page. Within the Master
page, you may add anything you like surrounding the
For example, you might add the logos you captured earlier, as shown in Figure
Figure 3. Editing the master page
For convenience, I've numbered three areas on Figure 3: the first image (1), the second image (2) and the
ContentPlaceHolder object (3). Notice also that the
ContentPlaceHolder tells you to click on it to add text. You may add text to the master page's
ContentPlaceHolder, which will act as default text (typically replaced in the pages that use this master page).
Adding Content Pages
The pages you'll add that will use this master page will put all of their content into the
ContentPlaceHolder you've added to the Master.
Note: You can put more than one
ContentPlaceHolderobject on a master page (each has its own ID), so this does not limit your flexibility.
To see how this works, create two new .aspx pages, named Welcome.aspx and SecondPage.aspx. Be sure to make these normal "Web Form" pages and be sure to check Select master page, as shown in Figure 4:
Figure 4. Creating a new Web Form to use with the master page
When you click the Add button, you will be brought to a dialog to select the master page you wish to use. Choose TopMasterPage.master and click OK. Your new Welcome.aspx page will be shown (in Design Mode) within the master page. The Content box will allow you to add any content you like, including controls, text, and so forth, as shown in Figure 5, but the contents of the master page will be disabled. This allows you to see how your new page will look when it is combined with the master page at run time.
Figure 5. Editing content inside of a master page
When you create SecondPage.aspx, you'll use the same master page, thus ensuring that the look and feel of the two pages is identical.
Using Sub-Master Pages
It is not unusual for you to want to have certain elements that are stable throughout the entire application, but other elements that are shared only within one part of your application. For example, you might have a company-wide header, but then have division-wide elements, as well. ASP.NET 2.0 lets you create sub-master pages. Any given .aspx page (web form) can be combined with a sub-master or with the original master, whichever makes more sense for that individual page.
To illustrate this, we'll create a sub-master page called OnDotNet.master. This sub-master page will have as its master page the TopMasterPage we created earlier, but it will add, within its Content control, an image and its own Content place holder (with its own default text). Unfortunately, you cannot use the designer (at least in its Beta form) to examine sub-master pages, but you can see the effect once you create an .aspx page that uses this sub-master. The code to create the sub-master is shown in Figure 6:
Figure 6. Hand-creating a sub-master page
The new sub-page has a Master directive, just like the topmost master page, but this sub-master adds one attribute:
MasterPageFile (shown highlighted in Figure 6) which is not in the topmost master page. This indicates that the current master page (OnDotNet.master) is a sub-master to TopMasterPage.master.
Pages: 1, 2