I was wondering what the best practis is for updating workflows in a live enviroment. Now during development I have noticed Serialization errors when building a new version of the workflow while having running workflows. It complains that "indexoutofbounds" when trying to featch the instance from the persistance service becouse there are more activities in the new version. How can i solve this
Workflow instance version issues
Hot Topic
- Qury Regarding Long Running Workflows ....
- If the session lost , how to make the long-running workflow going on
- Is the Task Dialog modal within its parent window or systemwide?
- Append Workflow to an existing solution
- WWF Thread Safety on Windows Forms
- InvokeWebService vs InvokeWorkflow
- Designer problem, VS extensions
- Casting property value in activity reference
- UnloadOnIdle no longer works in Web.Config.
- XOML Version (beta 1)
Windows Vista
- While Activity - Loss of status
- Horizontal flashes while drawing texture
- Windows workflow foundation and FileNet eProcess
- Passing DependencyProperty parameters into a dynamically created activity?
- Visual Studio Tools for windows workflow foundation
- isa 2004 switching to standby mode
- Error starting a workflow...
- Communication between 2 different workflows
- Persistence & tracking in beta 2.2
- Vista SDK Installation Failed
Workflow instance version issues
Sajal
You should use .NET assembly versioning to ensure that your published workflow models are identified as different by the CLR. Increment the version each time you publish an update. Any assemblies referenced by in-flight workflows need to be retained at the old version until such time as all those in flight workflow instances complete or you use the workflow change API's to update them.
The versioning issue with .NET assemblies can be avoided by not having any code beside and hence no .NET assembly related to your workflow model. This means declaring a workflow model entirely in XAML and in this case the workflow instance includes information about the model in the persisted state and there is no referenced .NET assembly.
Cheers,
Paul
Michael Nebel
Is there any documentation you could point me to for the "change APIs" so I could port old persisted workflows to my new versions
Ciaran