|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.|
Content Type Deployment Using Features
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.
Use the Feature packaging functionality in Windows SharePoint Services to install and activate content types.
Content types are a site-scoped Feature.
Features are a way of encapsulating Windows SharePoint Services functionality for ease of distribution and deployment. Features provide a mechanism by which developers can package the files a solution needs, such as content types, Web Parts, lists, and site definitions. Developers package the necessary files into a .wsp file, which is essentially a .cab file containing a manifest that lists its contents.
Inside the Feature, the feature.xml file contains references to all the element manifests within that Feature. Content type definitions are element manifests. You must create a content type definition for each content type included in your Feature.
For more information on content type definitions, see Content Type Definition Schema.
Site content types defined in one Feature can reference columns or content types contained in another Feature. In such a case, make the Feature referencing the contents of another Feature dependent on that Feature.
For more information about Features, see Working with Features.
Under no circumstances should you update the content type definition file for a content type after you have installed and activated that content type. Windows SharePoint Services does not track changes made to the content type definition file. Therefore, you have no method for pushing down changes made to site content types to the child content types.
For information about best practices when making changes to content types that have been installed and activated, see Updating Content Types.