Hi!

I'm trying to find the recommended approach to update the definition (xaml) of a workflow developed using VS 2013, when an earlier version of that workflow has already been deployed using a wsp. So imagine that I have a VS project with a package that includes a feature that includes a workflow definition and association files. i.e. standard approach for developing workflows using VS. I have deployed and activated the feature, now there are workflow instances running and the inevitable moment has come (either because a bug has been detected or some minor tweak needs to be done) that requires a new version to replace the current one.

I have taken the following under consideration already:

1) There is a known VS bug, accepted by MS. That one has to do with the development process and I'm already using the workaround mentioned there that involves killing a task after retracting the old wsp and deploying the new one. But I'm looking for a solution for my production environment and how to deploy the new version there.

2) I don't mind having existing instances to continue running with the previous version

3) Having experience with Workflow Foundation (outside the context of SharePoint) I understand that some changes can result in the deserialisation of running instances to fail. Nothing we can do about this.

4) I understand that one solution is to rename my project, change the guids and workflow name, deploy it as a completely new thing and disable the creation of new instances for the old one (as described here). But this would mean that updating workflows it not actually supported.

So what is the deal with this issue?