是否有用于编写可升级的 SharePoint 工作流的设计模式？
我在另一个线程上提出了有关升级长时间运行的工作流程的问题，但没有收到我想听到的答案。 （如何升级长期运行的 SharePoint 工作流生产中）
答案与我在该主题上所做的其他研究相匹配，建议以并排方法安装新的 WF（工作流），并将旧的 WF 标记为没有新实例。
我读到，如果新的 WF 具有相同的接口，那么可能只需替换原始 WF 的 dll，现有的长期运行的工作流程将继续运行。
是否有一种设计模式或指南可用于创建原始工作流，允许在产品的生命周期中进行代码更改，而无需替换每个 SharePoint 列表实例中的工作流？
I have asked a question on another thread about upgrading long running workflows and have not received an answer that I wanted to hear.
(How to upgrade a long running SharePoint Workflow already in production)
The answer, which matches up with the other research I have done on this topic, suggests installing the new WF (workflow) in a side by side method and marking the old WF as no new instances.
I have read that if the new WF has the same interface then there may be a possibility just replacing the original WF's dll and the existing long running workflows will continue to function.
Is there a design pattern, or guidelines, that would be useful in creating the original workflow allowing for code changes over the life-cycle of a product, without having to replace the workflow in each SharePoint List instance?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
SharePoint 中的工作流由两部分组成 - .net 代码和 xml 配置。
对于代码中的更改，您可以进行更改并重新部署解决方案包 - 只要程序集的强名称不更改，下次现有工作流上发生事件时就会调用新代码。 您只需要在进行更改时小心，确保您的代码不会假定工作流程是使用当前代码启动的。
xml 配置（实际上是工作流的接口定义）中的任何更改都将需要更完整的新部署。
There are two parts to a workflow in SharePoint - .net code and xml configuration.
For changes in the code, you can make changes and redeploy your solution package - as long as the strong name of the assembly doesn't change the new code will get called the next time an event occurs on an existing workflow. You just need to be careful when making changes that your code doesn't assume that the workflow was started using the current code.
Any changes in the xml configuration (effectively the interface definition for the workflow) will require the more complete new deployment.