<?xml version="1.0" encoding="utf-8" ?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <ListTemplate FeatureId="5DFD12AF-D0AA-4c63-8FB8-C49DB1191083" BaseType="0" Category="Custom Lists" Name="MyListTemplate" DisplayName="My List Template" Description="My Custom List Template." DisableAttachments="TRUE" DisallowContentTypes="TRUE" EnableModeration="FALSE" FolderCreation="FALSE" Hidden="FALSE" HiddenList="FALSE" OnQuickLaunch="TRUE" SecurityBits="11" Sequence="500" Type="100" VersioningEnabled="FALSE"> </ListTemplate> </Elements>
BaseType
- (required) Specifies the base type, or default schema, for lists created using this template. Like I mentioned in a previous post (WSS Tip #16: List Base Types) this attribute can have one of five possible values:- 0 (Generic List)
- 1 (Document Library)
- 3 (Discussion Forum)
- 4 (Survey)
- 5 (Issues List)
Category
- (optional) Specifies which category a list created from this template belongs to. It can assume one of the following values:- Libraries
- Communications
- Tracking
- Custom Lists
Type
- (optional) This attribute uniquely identifies this list template within the feature that contains it. SharePoint defines a set of list types which are used in the out-of-the-box list templates:- 100: Generic List
- 101: Document Library
- 102: Survey
- 103: Links List
- 104: Announcements List
- 105: Contacts List
- 106: Events List
- 107: Tasks List
- 108: Discussion Board
- 109: Picture Library
- 110: Data Source Gallery
- 111: Site Template Gallery
- 113: Web Part Gallery
- 114: List Template Gallery
- 115: XML Form Library
- 120: Custom Grid for a List
- 200: Meeting Series List
- 201: Meeting Agenda List
- 202: Meeting Attendees List
- 204: Meeting Decisions List
- 207: Meeting Objectives List
- 210: Meeting Text Box
- 211: Meeting Things to Bring List
- 212: Meeting Workspace Pages List
- 300: Portal Sites List
- 1100: Issue Tracking
- 2002: Personal Document Library
- 2003: Private Document Library
Content Type IDs
The content type ID uniquely identifies a content type and encapsulates the content type's hierarchy. That is, the ID of a certain content type includes the ID of its parent content type.
To create a new ID for a content type you can follow one of two possible conventions:
- [parent content type ID] + two hexadecimal values (different from "00")
- [parent content type ID] + "00" + hexadecimal GUID
Usually the first convention is used by SharePoint for the default content types included in SharePoint.
Example:
- 0x (System)
- 0x01 (Item Content Type)
- 0x0101 (Document Content Type, child of Item Content Type)
- 0x0120 (Folder Content Type, child of Item Content Type)
The second convention is used by SharePoint when
- You create a new content type based on an existing one
- A site content type is copied to a list (becoming a list content type)
You should use this convention whenever you create a new content type based on a content type you didn't create. If you're creating a content type based on another content type you have create, then you can use the first approach.
Example:
- 0x01 (Item Content Type)
- 0x0100C5647A362F236548B218C15302286758 (Custom Content Type based on the Item Content Type)
- 0x0100C5647A362F236548B218C1530228675801 (Custom Content Type based on the previous content type)