Workflow Foundation 4.0 - 事务服务& SQL 跟踪服务？
我正在探索 Workflow Foundation 4.0 是否足够稳定，可以开始在其上进行开发，但到目前为止我看到的文档神秘地没有说明为什么没有内置的 Transaction 和 Workflow Foundation 4.0。 SQL跟踪服务！它们在 WF 3.5 中可用并且似乎相当稳定。有什么线索吗？是 MS 没有时间按计划发布 WF 4.0，还是整个概念在 3.5 中被打破，他们决定废弃它们？我知道有很多链接和提示指向编写自定义（SQL）跟踪参与者，但是“框架”的意义何在？而且无法查询跟踪数据。没有任何关于交易服务的信息！那么我们如何保存WF持久化数据呢？应用数据一致吗？我在这里错过了什么吗？
关于 WF4 中“缺失”SQL 跟踪的一些令人不满意的答案：
- http://social .msdn.microsoft.com/Forums/en-US/wfprerelease/thread/8cfe598a-a400-4804-92ad-d68aa444d8f3
[还有更多链接，但无法在此处发布它们，因为新用户每个问题只能发布一个超链接:(]
任何帮助将不胜感激:)
I am exploring if Workflow Foundation 4.0 is stable enough to start developing on it but the documentations I've seen so far are mysteriously silent about why there are no built-in Transaction & SQL Tracking services! They were available in WF 3.5 and seemed to be reasonably stable. Any clues? Was there no time for MS to release WF 4.0 on schedule or the whole concept was broken in 3.5 that they decided to scrap them? I know there are lot of links and hints pointing to writing a custom (SQL) tracking participant, but then what is the point of a "framework"? Moreover there's no way to query the tracked data. And nothing about Transaction service! So how do we keep the WF persistence data & application data consistent? Am i missing something here?
Some unsatisfactory answers on "missing" SQL tracking in WF4:
- http://social.msdn.microsoft.com/Forums/en-US/wfprerelease/thread/8cfe598a-a400-4804-92ad-d68aa444d8f3
[got a few more links, but couldn't post them here bcoz new users can post only one hyperlink per question :( ]
Any help will be greatly appreciated :)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
缺少 SQL 跟踪，但如果您采用工作流服务路线，AppFabric 确实包含跟踪。
支持交易。有用于短期运行事务的 TransactionScope 活动和用于执行长时间运行事务的 CompensatableTransaction。还可以选择基于 PersistenceIOParticipant 创建活动扩展，您可以在用于保存工作流的事务期间保存额外的数据。
SQL tracking is missing however the AppFabric does include tracking if you go the workflow services route.
Transactions are supported. There is the TransactionScope activity for short running transactions an a CompensatableTransaction for doing long running transactions. There is also the option of creating activity extensions based upon PersistenceIOParticipant where you can save extra data durin THE transaction used to save THE workflow.
根据 MSDN，仍然支持 SQLTrackingService（请参阅以下文章的底部）：
http://msdn.microsoft.com/en-us/library/system.workflow.runtime.tracking.sqltrackingservice.aspx
您必须添加对 System.Workflow 的引用。 Runtime.dll（可能还有 System.Workflow.ComponentModel.dll）添加到您的项目中。确保项目属性中的目标是完整的 .net 4 框架（即不是客户端 .net 4 框架）。这两个 dll 都可以在 v4 框架目录中找到。
According to MSDN, the SQLTrackingService is still supported (see the bottom of the below article):
http://msdn.microsoft.com/en-us/library/system.workflow.runtime.tracking.sqltrackingservice.aspx
You will have to add references to System.Workflow.Runtime.dll (and probably System.Workflow.ComponentModel.dll) to your project. Make sure you are targeting the full .net 4 framework in your project properties (i.e. not the client .net 4 framework). Both dlls can be found in the v4 framework directory.