Hans Rasmussen

It seems like when you create workflows in Visual Studio and deploys them to SharePoint you have to consider the environment you are deploying them to. In the feature.xml the ReceiverAssembly and ReceiverClass are specified if you want to go for the MOSS 2007 deployment. Remove the lines in bold if you need to deploy them to WSS 3.0 installation.

<?xml version=”1.0″ encoding=”utf-8″ ?>

<Feature  Id=”Feature-GUID-Goes-Here”

      Title=”Thenameofyourfeature”

      Description=”The description of your feature”

      Version=”12.0.0.0″

      Scope=”Site”

      ReceiverAssembly=”Microsoft.Office.Workflow.Feature, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”      xmlns=”http://schemas.microsoft.com/sharepoint/“>

      ReceiverClass=”Microsoft.Office.Workflow.Feature.WorkflowFeatureReceiver”

  <ElementManifests>

    <ElementManifest Location=”workflow.xml” />

  </ElementManifests>

  <Properties>

    <Property Key=”GloballyAvailable” Value=”true” />

  </Properties>

</Feature>

Your workflow.xml however can look the same regardless of deployment

<?xml version=”1.0″ encoding=”utf-8″ ?>

<Elements xmlns=”http://schemas.microsoft.com/sharepoint/“>

  <Workflow

     Name=”Nameofyourworkflow”

     Description=”Description of your workflow”

     Id=”Workflow-GUID-Goes-Here”

     CodeBesideClass=”Projectname.Classname”

     CodeBesideAssembly=”Projectname.Classname, Version=1.0.0.0, Culture=neutral, PublicKeyToken=TokenForYourSignedDll”>

    <Categories/>

    <MetaData>

      <StatusPageUrl>_layouts/WrkStat.aspx</StatusPageUrl>

    </MetaData>

  </Workflow>

</Elements>