The first step in setting up the project is to add a new
project, which will be the web site (notice I started out with a blank
solution). This article uses the web application project template; the web site
template can be used by selecting Add > New Web Site option instead. I tend
to prefer the web application project model.
Figure 1
The next step is to setup the web site by giving it the name
of WebSiteStarterKit. Notice I am using the ASP.NET Web Application option.
Figure 2
Since this is a .NET 3.5 Framework project, the project
template sets up some of the AJAX features and .NET 3.5 components. Take a look
at the web.config file to see these new settings if you are unfamiliar with
them.
Let us start by adding an AJAX master page. To create the
master page, select the AJAX master page option, and give it the name of
Site.Master.
Figure 3
This template definition is a typical master page format,
plus a reference to the ScriptManager. Take a look at the following script
definition.
Listing 1
<%@ Master Language="C#" AutoEventWireup="true" CodeBehind="Site.master.cs"
Inherits="WebSiteStarterKit.Site" %>
<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title>Untitled Page</title>
<asp:ContentPlaceHolder ID="headPlaceholder" runat="server">
</asp:ContentPlaceHolder>
</head>
<body>
<form id="form1" runat="server">
<div>
<asp:ScriptManager ID="ScriptManager1" runat="server" />
<asp:ContentPlaceHolder ID="bodyPlaceholder" runat="server">
</asp:ContentPlaceHolder>
</div>
</form>
</body>
</html>
This is the base template of the initial master page;
however, to incorporate a wide array of features, I may create multiple master
pages. Multiple master pages create a personalized approach, and is expandable.
Alright, it is time to build in some features.
