<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Custom Event Receivers on Matt Thornton</title>
    <link>https://matt-thornton.net/tags/custom-event-receivers/</link>
    <description>Recent content in Custom Event Receivers on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 12 Sep 2011 08:18:36 +0000</lastBuildDate><atom:link href="https://matt-thornton.net/tags/custom-event-receivers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Provision Document Set &#43; XMLDocuments and ???</title>
      <link>https://matt-thornton.net/tech/sharepoint/provision-document-set-xmldocuments-and/</link>
      <pubDate>Mon, 12 Sep 2011 08:18:36 +0000</pubDate>
      
      <guid>https://matt-thornton.net/tech/sharepoint/provision-document-set-xmldocuments-and/</guid>
      
        <description>&lt;p&gt;SharePoint development is fraught with frustrations. Little things that should be simple, end up taking far longer than they should. Take this example. I&amp;rsquo;m trying to provision a Document Set content type via XML in a VS feature. I was using &lt;a href=&#34;http://www.youtube.com/watch?v=t3bynskrnpA&#34;&gt;this video&lt;/a&gt; and the &lt;a href=&#34;http://msdn.microsoft.com/en-us/library/gg581064.aspx&#34;&gt;supporting article&lt;/a&gt; as a guide. I get all the way through, and everything is working&amp;hellip; &lt;em&gt;ish&lt;/em&gt;. That is, the Document Set content type is created, but the extra stuff to do with it, such as the custom welcome page and the extra properties (shared fields, etc.), defined in the XmlDocuments section of the content type, don&amp;rsquo;t appear. No manner of tweaking and reducing code had any effect. I got a hold of the source code from the tutorial - lo and behold, that works fine. So the theory is sound, it &lt;em&gt;should&lt;/em&gt; work, and so something somewhere was different. The job was tracking down said difference.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>