I have a question concerning how to manage installation of new versions of workflow features, in case when there are already running instances. It seems on my development machine that after installing new package all running workflows are automatically stopped. It is not a problem now, but how this is going to be handled after deploying to production? Stopping everything after update will surely be problematic.
I see year ago someone had similar problem, no one knew the solution. Maybe this time it’s a bit better?
SharePoint 2013 Workflow Versioning
have you found solution?
Feb 5 ’15 at 14:21
nope, just keep deploying through VS each time…
Feb 10 ’15 at 5:47
The instruction how to update an existing workflow if itâ€™s necessary to make changes to the workflow, but all running workflows must keep going:
Add ReplaceContent=”TRUE” to Elements.xml files of workflow and workflow activities.
Create a wsp package with updated workflow/workflow activities.
Update the solution using the Update-SPSolution cmdlet.
Force enable the workflow and workflow activity features using the
Enable-SPFeature â€“force cmdlet.
Look at my question and answer for details.
I’ve merged the two questions into one (and up-voted your answer)
– Benny Skogberg♦
Dec 7 ’15 at 13:27