Understanding Content Type IDs and a Reference

By -
Microsoft provides a very thorough explanation of ContentTypes here but you may be left wondering what content types you can inherit from (or more likely what are their content type IDs) so you can build off of them. Well you can always go look at them in the 'ctypes' feature folder (that's the out-of-box feature that defines the WSS content types). It's available at under your 12\TEMPLATE\Features\ctypes folder in the 'ctypeswss.xml' file.

Otherwise you can just refer to this list I pulled together:

0x : System
0x01 : Item
0x0101 : Document
0x010100629D00608F814dd6AC8A86903AEE72AA : ODCDocument
0x010100B4CBD48E029A4ad8B62CB0E41868F2B0 : UDCDocument
0x010101 : XMLDocument
0x010102 : Picture
0x010104 : UntypedDocument
0x010105 : MasterPage
0x010107 : DocumentWorkflowItem
0x010108 : WikiDocument
0x010109 : BasicPage
0x01010901 : WebPartPage
0x01010A : LinkToDocument
0x01010B : DublinCoreName
0x0102 : Event
0x0103 : Issue
0x0104 : Announcement
0x0105 : Link
0x0106 : Contact
0x0107 : Message
0x0108 : Task
0x010801 : WorkflowTask
0x010802 : AdminTask
0x0109 : WorkflowHistory
0x010A Person
0x010B SharePointGroup
0x010C DomainGroup
0x0110 : BlogPost
0x0111 : BlogComment
0x0116 : FarEastContact
0x0120 : Folder
0x012001 RootOfList
0x012002 : Discuss

By the way, I got this list by copying/modifying the files I used in this post to refer to the ctypeswss.xml file instead of the field types file.

Comments

Post a Comment

Popular posts from this blog

Programmatically Update Page Layouts

By -
I updated my page layouts that I deployed as a feature, but found that I could not overwrite the Layout File. The solution was to add a new page layout and then you would have to associate the new layout with every page on your site that used it. Obviously with a site of any size you'd have a lot of manual work to get this done, so doing it programmatically makes for a much better (and thorough) approach. After you've got your new page layouts, you could do something like this (in your event receiver class): public override void FeatureActivated(SPFeatureReceiverProperties properties) { //replace current page layouts with new page layouts on all pages SPWeb web = SPContext.Current.Web; SwapPageLayout(web, "FullWidthContentWithTitleV1.aspx", "FullWidthContentWithTitleV2.aspx"); } private void SwapPageLayout(SPWeb web, string oldPageLayoutName, string newPageLayoutName) { PublishingWeb pubWeb = PublishingWeb.GetPu...
Read more

Microsoft Virtualilzation Headaches

By -
As a SharePoint consultant, I am constantly moving from client to client and the best way to develop and test the code, designs and configurations for each client while maintaining complete separation is to virtualize. Since I work for a Microsoft partner, we try to use Microsoft tools and technologies as much as possible, which can be quite frustrating, as you will find out below. I recently started working for a large client with a global presence whose IT policies are well-established, difficult to change and not always up-to-date. In that vein, enter the corporate VPN: it's a web-based signin with a host checker that doesn't support any x64 OS. This prompted me, running Win 7 x64, to try to get a co-worker's Hyper-V Win2k3 x86 MOSS VM and run it in Windows Virtual PC . Seems like a logical thing to do, right? I mean, a Microsoft VHD should work, and be able to be imported by other Microsoft tools, right? Wrong. After spending quite a bit of time trying to attach the VHD...
Read more

ERROR: Failed to create feature receiver...

By -
I was working on a STSDev project which deployed a feature with a feature receiver. I had the feature working without the FeatureReceiver but as soon as I added the FeatureReceiver related attributes to my <Feature> element I got the following error: Failed to create feature receiver object from assembly "Org.Project.Solution, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c632353d405b3209", type "Org.Project.Solution.MyFeature.FeatureReceiver" for feature 6a9b2358-ea4e-486d-a4e4-4f813c52ce88: System.ArgumentNullException: Value cannot be null. Parameter name: type at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() After much digging around I discovered that STSDEV's Solution config file refers to a namespace as well as the dll. My FeatureReceiver's namespace was not prefixed with the right namespace So just...
Read more