Custom Information in Content Types
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
By design, content types are extensible. You can include custom information in content type definitions by adding special XML nodes. These XML nodes are represented by the XmlDocument Element (ContentType) element in the content type definition, and you can access them programmatically through the object model. A content type can include any number of XMLDocument elements. The contents of each XMLDocument element can conform to any given schema; however, they must be valid XML.
By including your custom information within XMLDocument elements in the content type, you can ensure that the custom information you need to implement your solution is encapsulated within and becomes part of the content type.
XMLDocument elements included in a site content type are also copied into any children based on that content type.
You can add this information to a content type in two ways:
Before provisioning the content type, as an XmlDocument Element (ContentType) element contained in the content type definition XML used to provision the content type.
For more information, see Content Type Definition Schema.
After provisioning the content type, by using the Add method of the SPXmlDocumentCollection object in the Windows SharePoint Services 3.0 object model.
If you make a change to an XML document and then perform a push-down operation, the entire XML document is overwritten in any child content types. For more information, see Updating Child Content Types.
XML Document Schemas Included with Windows SharePoint Services
Windows SharePoint Services 3.0 itself includes pre-defined XML documents you can use to specify custom forms for a content type, or to specify client-side redirects to different form pages for a content type.
This schema enables you to specify the form templates used to display an item's Display, New, and Edit pages in the Windows SharePoint Services 3.0 user interface.
This schema enables you to specify client-side redirects to different Display, Edit, and New form pages for items of this content type.