4.0中的工作流持久性，仍然是二进制序列化吗? [英] Workflow persistence in 4.0, still binary serialization?

问题描述

您好，

3.5版中持久化工作流程的版本控制使我们对.net wf的实现降至最低.任何人都可以描述4.0中可能减轻升级"功能带来的痛苦的任何更改.

我已经阅读了所有建议并感谢您的投入，但是可能让数百个(如果不是数千个)工作流实例完成".通过GAC中的版本化程序集在我们的代码库的先前版本上是不可行的.

在此先感谢，

Derrick

Hello,

The versioning aspect of persisted workflows in 3.5 has kept our implementation to a minimum with respect to .net wf.  Can anyone describe any changes in 4.0 that might have eased the pain of "upgrading" a long running and persisted workflow to a new version of that workflow?

I've read all the suggestions and appreciate the input, but letting potentially hundreds if not thousands of workflow instances "finish" on a prior version of our code base via versioned assemblies in the GAC is not an option for us.

Thanks in advance,

Derrick

推荐答案

Derrick，我可以说，首先，迁移工作流程是从旧模式"开始的.是不支持的，我可以说这是不安全的，因为您不能期望完全控制迁移过程.

Hi Derrick, I can say that first of all, migrating workflows started with an "old schema" is something that is not supported, and let me say, unsafe, because you can't expect to have complete control on the migration process.

这篇关于4.0中的工作流持久性，仍然是二进制序列化吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！