There is a nice article that demostrates the API mapping between CMS 2002 and Sharepoint 2007 with lots samples. This is a the best one I found so far for programming WCM in Sharepoint 2007.
http://msdn.microsoft.com/library/en-us/dnmscms02/html/CMSVersionAPIDiffs.asp?frame=true
Sunday, July 09, 2006
MOSS 2007 and WSS 3.0 Master Page
It would be a very bad experience if you have ever tried to change the interface of Sharepoint Portal 2003. But MOSS 2007 and WSS 3.0 bring a new concept: the master page. The master pages are same as master pages used in ASP.NET 2.0. They define the look and feel and standard behavior in your site and make the customization a lot easier.
Master page combined with the page layouts, the content type, it produces the output of the pages with standard feel and look. The page layout is similar to the content page in
ASP.NET 2.0, which points to a master page and implements the content placeholders.
By default, the master page used in MOSS 2007 or WSS 3.0 is side wide. It means when you change the master page, it effects the look and feel changes in all pages in the site. These master pages are referenced as two dynamic tokens.
Two Dynamic Tokens
~masterurl/default.master
This token is used for the look and feel of all forms and views within the site, usually these pages are under _layouts directory. It is also called “Default master page” in Sharepoint Designer or “System Master Page” in “Site Settings\Look and Feel\Site Master Page Settings”. This master page token is used in the code of page layout page as
Page language="C#" MasterPageFile="~masterurl/default.master" ...
When Sharepoint loads the page, the token “~masterurl/default.master” is replaced at run time by the value in MasterUrl property of SPWeb.
To specify a master page for this token, by browser you can navigate to Site Settings\ Look and Feel\Site Master Page Settings, and select a master file from “System master page” dropdown as following picture.
Static Tokens
There are two static tokens for WSS 3.0 sites. If you the master page is in the master page gallery of the site, you can use it in your page by adding MasterPageFile=“~site/xxx.master”
If the master page is defined in the master page gallery in the root site, you can use by adding MasterPageFile=“~sitecollection/xxx.master” in your page.
DefaultPageLayout.aspx and Page Layouts
DefaultLayout looks like a special layout page defines the default layout for all publishing pages cross the site. The interesting thing is when you inspect the MasterPageFile attribute in all page layout aspx files, only DefaultLayout.aspx contains MasterPageFile attribute and its value is “~masterurl/custom.maseter”. The DefaultLayout.aspx is inherited from Microsoft.SharePoint.WebPartPages.WebPartPage but other page layouts including the page layouts created by you are inherited from Microsoft.SharePoint.Publishing.PublishingLayoutPage.
So I guess the PublishingLayoutPage class is somehow related to DefaultLayout.aspx, at least the master page of Defaultlayout.aspx will be re-used for all page layouts inherited from PublishingLayoutPage. So if you want to create a page layout use another master page instead of the Site Master Page (Custom master page), you need to change the base class from PublishingLayoutPage to WebPartPage and set the MasterPageFile attribute.
Master page combined with the page layouts, the content type, it produces the output of the pages with standard feel and look. The page layout is similar to the content page in
ASP.NET 2.0, which points to a master page and implements the content placeholders.
By default, the master page used in MOSS 2007 or WSS 3.0 is side wide. It means when you change the master page, it effects the look and feel changes in all pages in the site. These master pages are referenced as two dynamic tokens.
Two Dynamic Tokens
~masterurl/default.master
This token is used for the look and feel of all forms and views within the site, usually these pages are under _layouts directory. It is also called “Default master page” in Sharepoint Designer or “System Master Page” in “Site Settings\Look and Feel\Site Master Page Settings”. This master page token is used in the code of page layout page as
Page language="C#" MasterPageFile="~masterurl/default.master" ...
When Sharepoint loads the page, the token “~masterurl/default.master” is replaced at run time by the value in MasterUrl property of SPWeb.
To specify a master page for this token, by browser you can navigate to Site Settings\ Look and Feel\Site Master Page Settings, and select a master file from “System master page” dropdown as following picture.
~masterurl/custom.master
This token is used for all publishing pages within the site. It’s also called “Custom master page” in Sharepoint Designer or “Site Master page” in “Site Settings\Look and Feel\Site Master Page Settings”. When you open the DefaultLayout.aspx, you will see the code like,
Page language="C#" MasterPageFile="~masterurl/custom.master" …
At run time, this token is replaced by the value in CustomMasterUrl of SPWeb object.
You can change the master page specified for this token in “Site Master Page” drowdown in Site Settings\ Look and Feel\Site Master Page Settings.
Also, these master page tokens are able to be changed in Sharepoint Designer by right click on the master page and select “Set as Default master page” or “Set as custom master page”.
Static Tokens
There are two static tokens for WSS 3.0 sites. If you the master page is in the master page gallery of the site, you can use it in your page by adding MasterPageFile=“~site/xxx.master”
If the master page is defined in the master page gallery in the root site, you can use by adding MasterPageFile=“~sitecollection/xxx.master” in your page.
DefaultPageLayout.aspx and Page Layouts
DefaultLayout looks like a special layout page defines the default layout for all publishing pages cross the site. The interesting thing is when you inspect the MasterPageFile attribute in all page layout aspx files, only DefaultLayout.aspx contains MasterPageFile attribute and its value is “~masterurl/custom.maseter”. The DefaultLayout.aspx is inherited from Microsoft.SharePoint.WebPartPages.WebPartPage but other page layouts including the page layouts created by you are inherited from Microsoft.SharePoint.Publishing.PublishingLayoutPage.
So I guess the PublishingLayoutPage class is somehow related to DefaultLayout.aspx, at least the master page of Defaultlayout.aspx will be re-used for all page layouts inherited from PublishingLayoutPage. So if you want to create a page layout use another master page instead of the Site Master Page (Custom master page), you need to change the base class from PublishingLayoutPage to WebPartPage and set the MasterPageFile attribute.
Friday, July 07, 2006
New blog
I have created a new blog on www.sharepointblogs.com/jimyang. I will move most of my Sharepoint posts to there, but I will keep posting new articles on both sides.
Wednesday, July 05, 2006
Master Page and Page Layout ?
According to MOSS 2007 document, master page and page layout are working together as a template to control content pages' look, feel and content. In top site, there is a "Master page and Page Layout Gallery" and you could find lots out-of-box master and page layout (aspx) file there.
But I am frustrating in finding the relationship between master page and the page layout. It's able to create/upload many master pages or create many page layout, but I found all new page layout use default.master as master page and couldn't find a way to associate to other master page.
Does anybody know the answer?
But I am frustrating in finding the relationship between master page and the page layout. It's able to create/upload many master pages or create many page layout, but I found all new page layout use default.master as master page and couldn't find a way to associate to other master page.
Does anybody know the answer?
Tuesday, July 04, 2006
Tips on Sharepoint Search Include Exclude path configuration
Last year when I was working on an enterprise search project with SPS 2003, I was frustrating on getting the rules that include or exclude content from content index work. I called Microsoft and I spent 3 hours with a Microsoft guy on the phone but got nothing useful.
After many hours testing by myself, I found the order or the include/exclude rules in a content index is very important and effects your search result enormously (But MS told us this doesn't matter.). I guest it is because each time when the search engine will index an URL, it first tests this URL against all rules one by one, and when it reaches the first satisfied rule, on matter it is an inclusion or exclusion rule, it returns immediately and ignores all following rules. For instance,
include: http://server/abc/*
exclude: http://server/abc/def/* ---- not working because the inclusion rule on top run first and block this exlcusion rule.
After many hours testing by myself, I found the order or the include/exclude rules in a content index is very important and effects your search result enormously (But MS told us this doesn't matter.). I guest it is because each time when the search engine will index an URL, it first tests this URL against all rules one by one, and when it reaches the first satisfied rule, on matter it is an inclusion or exclusion rule, it returns immediately and ignores all following rules. For instance,
include: http://server/abc/*
exclude: http://server/abc/def/* ---- not working because the inclusion rule on top run first and block this exlcusion rule.
Subscribe to:
Posts (Atom)