|
|
|
|
|
|
|
|
|
|
|
|
|
page 148
The following CAML is used to create an Issues list instance. issues_Folder does not exist and should be replace with issuesList in the following code:
<List FeatureId="00BFEA71-5932-4F9C-AD71-1557E5751100" Type="1100" Title="$Resources:core,issuesList;" Url="$Resources:core,lists_Folder;/$Resources:core,issues_Folder;" QuickLaunchUrl="$Resources:core,lists_Folder;/$Resources:core,issues_Folder;/AllItems.aspx" />
The error caused by this typo looks like this:
I provide a sample VS.NET project with an entire working site definition here. Please also see related error on page 150 (later on this page).
page 149
The side bar states that the URL is limited to 260 characters. In WSS v2, this was true. In WSS v3, it's possible to create URLs considerably longer than 260 characters (perhaps a max of 1155 characters). The suggestion not to use spaces still stands, but the number is innacurate.
page 150
issues_Folder does not exist and should be replace with issuesList in the following code:
<View List="$Resources:core,lists_Folder;/$Resources:core,issues_Folder;" BaseViewID="0" WebPartZoneID="Left" WebPartOrder="3" />
Please see the related error on page 148 (earlier on this page).
page 150ff
This section had some typos and step #2 wasn't needed at all.
Add a Custom Master Page
This Master pages in WSS v3 replace the old direct-mode page paradigm from WSS v2. Master pages are referenced in the page directive or in code. Therefore, master pages will always be referenced, even if a page is customized (unghosted). This is a huge improvement over the approach used in WSS v2 because global change can nearly always be achieved regardless of how much the instance pages of any website are customized. Customizing Master Pages using SPD will throw a wrench in this.
Use the following steps to add a master page and set the default.aspx Template page to use the custom master page rather than the default master page defined by Microsoft:
-
In the VS.NET Solution Explorer, right-click on the STS2 project name and choose Existing Item... from the Add context menu.
-
Browse to the 12 Hive’s ..\12\TEMPLATE\GLOBAL directory. To add a copy of the default.master page from here, the Files of type must be changed to All Files (*.*). Choose the default.master file and click Add. A copy of the master page is added to the Solution Explorer.
-
Rename the copied file to something like: sts2.master. It must end with the master suffix.
-
Alter the master page to meet the business needs. For this exercise, add a large header to the top of the page that says STS2 Custom Master Page by placing the following code just after the master page’s BODY tag:
<h1>STS2 Master Page</h1>
-
To make the custom site definition aware of the new custom master page, add the following Module to the Modules section at the bottom of the ONET.XML file:
<Module Name="STS2MasterPage" Url="_catalogs/masterpage">
<File Url="sts2.master" Type="GhostableInLibrary" />
</Module>
This module tells WSS v3 to include a link (GhostedInLibrary) to the sts2.master page in the Master Page Gallery found at _catalogs/masterpage. The module is named STS2MasterPage.
- The module will only be included if a call is made to it at the configuration that the user selects. Add the following code to the Modules section of the configuration to call the STS2MasterPage module in the configuration:
<Module Name="STS2MasterPage" />
- Set the CustomMasterUrl attribute of the configuration element to use the custom master page like this:
<Configuration ID="0" Name="Default"
CustomMasterUrl="_catalogs/masterpage/STS2.master">
- Finally, the Template page to use the custom master page token by specifying the MasterPageFile attribute of the page directive like this (the default value):
<%@ Page language="C#" MasterPageFile="~masterurl/custom.master"
Rebuild the project to copy the WEBTEMP*.XML file and recycle the application pool to test the new site definition.
HTH,
<Todd />
|
Last modified at 4/10/2007 2:09 PM by Todd Bleeker
|
|
|
|
 |
|
|
|
|