<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Workflowfeature on Matt Thornton</title>
    <link>http://localhost:1313/tags/workflowfeature/</link>
    <description>Recent content in Workflowfeature on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Fri, 06 May 2011 16:46:46 +0000</lastBuildDate><atom:link href="http://localhost:1313/tags/workflowfeature/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tip: Error occurred in deployment step Activate Features: Object not set to an instance of an object</title>
      <link>http://localhost:1313/tech/sharepoint/tip-error-occurred-in-deployment-step-activate-features-object-not-set-to-an-instance-of-an-object/</link>
      <pubDate>Fri, 06 May 2011 16:46:46 +0000</pubDate>
      
      <guid>http://localhost:1313/tech/sharepoint/tip-error-occurred-in-deployment-step-activate-features-object-not-set-to-an-instance-of-an-object/</guid>
      
        <description>&lt;p&gt;Yet another SharePoint vagary. If you&amp;rsquo;re trying to deploy a feature and get the unhelpful error: “Error occurred in deployment step ‘Activate Features&amp;rsquo;: Object not set to an instance of an object” check the &lt;strong&gt;scope&lt;/strong&gt; of the feature that you&amp;rsquo;re trying to deploy. I added a new feature to a project that had another working feature. Both were calling the Microsoft.Office.Workflow.Feature assembly but only one was failing and it was only after a lot of messing about that it turned out to be this innocuous little setting.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>