Wss3sdk: custom information in the content type

The content type is designed as a scalable structure. You can add a specific XML node in the content type definition to contain custom information. In the definition of content types Xmldocument Element (It is an xmldocument used for content. WSS has many xmldocument elements and is independent of each other) You can use the object model Code . A content type can contain any number Xmldocument Element. Xmldocument The content of the element can match any given architecture. However, the content must be a valid XML.
By adding custom information to the xmldocument element of the content type, you can ensure that the required custom information is integrated with your solution and can be deployed as a package.
The xmldocument element contained in the website content type will also be copied to all child generations based on this content type.
You can add custom information in two ways:
Before the content type is not activated on the website, it is Xmldocument Element.
After the content type is activated on the website, you can Spxmldocumentcollection Object Add Method to add.
If you modify the XML document and perform the push operation, the entire XML document will be overwritten in the sub-content type.
XML document architecture contained in WSS

WSS itself contains some pre-defined XML documents. You can customize a content type form or specify a client for a content type to redirect to different forms pages.
Formtemplates Architecture
This architecture allows you to specify a form template for displaying, creating, or editing display items on the WSS 3.0 user interface.

Formurls Architecture

This architecture allows you to specify the client redirect page for the list item that applies this content type to display, edit, or create a page to redirect to another URL.