Custom Field Types Deployment
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.
Custom field types are deployed at the server farm-level, using the Windows SharePoint Services Solution Deployment functionality.
The various pieces of a custom field type solution must be deployed to the following locations:
The field type class must be deployed as a strong-named assembly to the global assembly cache.
The field type definition XML file must be deployed to the same location as fldtypes.xml, the XML file that defines the base Windows SharePoint Services 3.0 field types:
\program files\...\web server extensions\12\template\xml\
Each field type definition must be included in a file named fldtypes*.xml. For example, if you have a field type definition for a field type that defines a Social Security Number, you might name the XML file fldtypes_ssn.xml.
If you have specified a custom field editor user control for the field type, it must be deployed to the following location:
\program files\...\web server extensions\12\template\controltemplates\
For more information about deploying your field type as a solution, see Solutions and Web Part Packages. For the specific steps to create a solution, see Creating a Solution.