• Mar 7, 2009

    ContentPlaceHolder trick

    • ContentPlaceHolder in master page is reference in Content control in content page
    • Content control's Id can be empty, but the ContentPlaceHolderID need to be filled. The position of Content control in content page does not matter.
    • In ContentPlaceHolder, you can fill in some default content. But they will be override once content page reference it.
  • Mar 5, 2009

    Global Site Definition

    The Global site definition is located at the 12\TEMPLATES\GLOBAL path. It contains the standard default.master page template along with instructions to provision an instance of default.master page into the Master Page gallery of every new site. The Global site definition also contains provisioning logic to create the following four site collection–scoped lists in every new top-level site:Web Parts gallery, List Template gallery, Site Template gallery, User Information Profile list

  • Mar 5, 2009

    Site Definition vs Site Template

    Site definition are deployed within 12\template\sitetemplates directory and are referenced in 12\template\1033\xml\webtemp*.xml files Wss offer site definitions to provide users with createable site templates out of the box. A site definition named sts prvoides familar site templates such as Team Site, Blank site, and document workspace. </p>

    A site definition itself does not represent a creatable site template. Instead, a site definition contains one or more configurations, and these configurations are what appear to users as creatable site templates.

    Site definition --contains--> configurations <--referenced by webtemp*.xml --> display configuration as creatable site template

    When creating a new site by using the STSADM.EXE command-line utility or through custom code, you are often required to reference a site definition and one of its configurations by name. This is done by specifying the name of the site definition followed by the pound sign and the integer identifier of the configuration. For example, you can use STS#0 to reference the site template titled Team Site and STS#1 to reference the site template titled Blank Site. The following example uses one of these site template references when creating a new top-level site by using the STS command-line utility.

  • Mar 5, 2009

    Changing a built-in site definitions and templates

    One of the challenges in WSS 2.0 was adding new functionality to existing site definitions and templates. This was because the official guidance from Microsoft was to never edit an existing site definition or template once sites have been provisioned using it, and that developers should not modify the site definitions provided in the out - of - the - box installations, as future updates (hotfixes and service packs) could overwrite the files. To address this, Microsoft added the capability of Feature stapling.

  • Mar 5, 2009

    Feature used to activate other feature

    Sometime you can use a feature simply to activate other features.