Page Processing Model

As with Microsoft Content Management Server 2002, Microsoft Office SharePoint Server 2007 is a template-based page rendering system. The two fundamental templates used for page rendering in SharePoint sites are master pages and page layouts. Master pages can be used by all page instances in a site. Page layouts can be used by all page instances that are based on that page layout. Page layouts are stored as list items in the Master Page and Page Layout Gallery, so you can use versioning, check-in and check-out, workflow, and other features available for SharePoint document libraries.

Office SharePoint Server 2007 is built on top of Windows SharePoint Services 3.0 and Microsoft ASP.NET 2.0. The ASP.NET engine interprets and runs all SharePoint page requests. For example, suppose a user requests a page named welcome.aspx in the browser. The ASP.NET engine retrieves the page layout associated with the page and the master page associated with the site via the Windows SharePoint Services 3.0 FileProvider object, and it renders the field controls and Web Parts from the fields onto the page. The following figure shows the page processing model in Office SharePoint Server 2007.

The Page Processing Model

The following list gives a step-by-step breakdown of how ASP.NET 2.0 and Windows SharePoint Services 3.0 interact to render pages in a SharePoint site:

1. The browser requests a Web page from Microsoft Internet Information Services (IIS).
2. IIS passes the request to ASP.NET 2.0.
3. An HttpApplication pipeline is created for the request.
4. ASP.NET 2.0 fetches the page via the Windows SharePoint Services 3.03 file provider. ASP.NET passes the URL to the file provider, and the file provider fetches the page and returns the page stream. The Windows SharePoint Services file provider implements caching and reduces round-trips to the database.
5. ASP.NET loads a Page class, parses the page stream, and finds a reference to the page layout upon which the page is based.
6. The ASP.NET engine compiles the page stream and stores it in memory.
7. ASP.NET queries the Windows SharePoint Services file provider for the page layout.
8. ASP.NET loads the stream for the page layout associated with the current page.
9. ASP.NET compiles the page layout and stores it in memory. ASP.NET can free this memory later if the system needs memory.
10. ASP.NET determines the master page for the site and fetches the master page via the Windows SharePoint Services file provider.
11. ASP.NET compiles the master page and writes to the disk so you never have to recompile the master page unless you modify it.
12. The page layout runs each control on the page in the context of the page that was requested.
13. ASP.NET updates the necessary caches.
14. IIS returns the page to the browser.

The next time the page is requested by the same user or by a different user who has the same permissions to see the page as the first user, page processing is much more efficient:

1. The browser requests a Web page from IIS.
2. IIS passes the request to ASP.NET 2.0.
3. An HTTPApplication pipeline is created for the request and hits the HandleRequest.
4. ASP.NET uses all the internal caches.
5. ASP.NET renders the HTML for the controls.
6. IIS returns the page to the browser.
   
   
   Refered From: http://msdn.microsoft.com/en-us/library/ms498550(v=office.12).aspx

   
   

   
   

   When a site visitor requests a page, SharePoint combines content and templates from the site to render the fi nal page. SharePoint begins by retrieving the requested page from the Page library. This provides SharePoint with the metadata that identifi es the web page, as well as the content that the author entered into the page. Next, SharePoint retrieves the Master Page and the Layout page from the Master Pages and Page Layouts gallery. SharePoint determines the correct page layout by
   examining the content type of the requested web page. Finally, SharePoint combines the Master Page, Layout page, and content into a rendered HTML page that it sends back to the end user ’ s browser.

   There is an important relationship between the templates and content that is defi ned by content types. The content type is a container for the site columns that defi ne the content and metadata for the web pages. As the container for this information, the content type acts as the glue between the content and the templates. The content type is assigned to both the template and the Pages library. This allows the template to use placeholders that align to the site columns, and it allows the author to use the template within the site.

Create managed metadata column using feature

Create managed metadata column using feature

I have seen lots of blogs which talks about creating managed metadata column via feature but I haven’t got a single article which provided me a complete solution. In this blog, I am going to talk on creating managed metadata column using feature and assigning it a to proper term set.

Click here to download the sourecode.

Pre-requisites.

Create a Managed metadata column with the below settings.

•  Group Name: Electronics
• Term set: Computer
• Term:  Dell, Samsung, HP

Below is the screen shot after creating the column.

 Creating Column via Feature.

1.       Open Visual Studio and create an Empty SharePoint Project(  I have named as ManagedMetadata_Column)

2.       Add a New Item. Select Empty Element.

 3. Paste the below section in between the elements tab. 

  <Field DisplayName="MMSingleSelect"

       ID="{D069F181-5674-4D87-BDA8-2AC3CE6F6E39}"

       Type="TaxonomyFieldType"

       DisplaceOnUpgrade="TRUE"

       Required="FALSE"

       Group="Simple Rule Site Columns"

       SourceID="http://schemas.microsoft.com/sharepoint/v3"

       StaticName="MMSingleSelect"

       Name="MMSingleSelect"

       Overwrite="TRUE">

  </Field>

  <Field DisplayName=" MMMultiSelect"

         ID="{B1D07B1A-60B9-40A9-A53C-48BAB6FABD23}"

         Type="TaxonomyFieldTypeMulti"

         DisplaceOnUpgrade="TRUE"

         Required="TRUE"

         Mult="TRUE"

         Group="Simple Rule Site Columns"

         SourceID="http://schemas.microsoft.com/sharepoint/v3"

         StaticName="MMMultiSelect"

         Name="MMMultiSelect"

         Overwrite="TRUE">

  </Field>

4. Above section adds 2 columns with Multi Select enabled and another one with Multi Select disabled.

Click on the feature and click on the Add event Receiver. This will add new cs class. Uncomment the FeatureActivated method and paste the below code. Basically, this code will read the field and will update the column values. This code is self-explanatory

public class Managed_Metadata_ColumnEventReceiver : SPFeatureReceiver

{
public const string METADATA_SERVICE = "Managed Metadata Service";
public const string MMSingleSelect = "MMSingleSelect";
public const string MMMultiSelect = "MMMultiSelect";
public const string ATTRIBUTE_GROUP = "Electronics";
public const string TERMSET = "Computer";
public override void FeatureActivated(SPFeatureReceiverProperties properties)
{
SPWeb currentWeb = null;
XmlDocument fieldDefinition = null;
XPathNavigator fieldNavigator = null;
XPathNodeIterator selectedNodes = null;
try
{
// feature is scoped at Site, so the parent is type SPSite rather than SPWeb..
using (SPSite site = properties.Feature.Parent as SPSite)
{
if (site != null)
{
currentWeb = site.RootWeb;
}
using (currentWeb)
{
string listName = string.Empty;
string columnName = string.Empty;
string groupName = string.Empty;
string finalCaml = string.Empty;
string hiddenListId = string.Empty;
string webId = string.Empty;
fieldDefinition = new XmlDocument();
fieldDefinition.LoadXml(currentWeb.Fields.SchemaXml);
fieldNavigator = fieldDefinition.CreateNavigator();
fieldNavigator.MoveToRoot();
selectedNodes = fieldNavigator.Select("//Field[@Type='TaxonomyField'] | //Field[@Type='TaxonomyFieldType'] | //Field[@Type='FilteredLookupTextField']| //Field[@Type='TaxonomyFieldTypeMulti']");
while (selectedNodes.MoveNext())
{
groupName = selectedNodes.Current.GetAttribute("Group", string.Empty);
if (groupName == "Simple Rule Site Columns")
{
TaxonomySession session = new Microsoft.SharePoint.Taxonomy.TaxonomySession(site);
TermStore termstore = session.TermStores[METADATA_SERVICE];
columnName = selectedNodes.Current.GetAttribute("Name", string.Empty);
TaxonomyField taxonomyColumn = currentWeb.Fields.GetFieldByInternalName(columnName) as TaxonomyField;
currentWeb.AllowUnsafeUpdates = true;
switch (columnName)
{
case MMSingleSelect:
SetTaxonomyTermSet(termstore, taxonomyColumn, session, ATTRIBUTE_GROUP, TERMSET);
break;
case MMMultiSelect:
SetTaxonomyTermSet(termstore, taxonomyColumn, session, ATTRIBUTE_GROUP, TERMSET);
break;
}
}
currentWeb.AllowUnsafeUpdates = false;
}
}
}
}
catch (Exception ex)
{
//
}
}
private void SetTaxonomyTermSet(TermStore termstore, TaxonomyField taxonomyColumn, TaxonomySession session,string termStoreGroup, string termSet)
{
Group group = termstore.Groups[termStoreGroup];
TermSet termset = group.TermSets[termSet];
taxonomyColumn.SspId = termstore.Id;
taxonomyColumn.TermSetId = termset.Id;
taxonomyColumn.Update();
}
}

 

5. Once the WSP is deployed and go activate the feature ManagedMetadata_Column Feature. You should see 2 column created under "Simple Rule Site Columns".

Click here to download the sourecode.