SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We need help from experts regarding workflows deployment strategies.

We have several state machine workflows created using VS-2010, now after deployment, Client will ask for changes inside it e.g. adding activities e.t.c how do we re-deploy it ?

share|improve this question

The simple answer is:

  • Update the AssemblyVersion in References.cs
  • Update the version number in CodeBesideAssembly in workflow.xml
  • Make the changes to the workflow
  • Deploy

But the big question is then how do you want running instances of the workflow to behave and hopefully you thought about this before you deployed the first version. For more information about your options see Versioning a Visual Studio SharePoint Workflow

share|improve this answer
up vote 0 down vote accepted

After research and analysis i posted a blog post, it contains all information related to re-deployment or upgrading visual studio created workflows in SharePoint 2010, i hope this post will save some time of dev's looking for similar information.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.