Windows 工作流基础。我应该使用它吗？
我正在开发一个我怀疑适合使用工作流程的应用程序。 （很容易可视化不同用户之间的物理工作流程和任务。）
我的问题是使用这种方法有什么优点，你建议我走这条路吗？有没有更好的方法。
我听说过性能上的成功？这值得考虑吗？
最后，谁能推荐一本关于工作流程的好书吗？
更新： 我的解决方案的简要概述 - 从基本角度来说，它是一个预订/活动/日记系统。 “模型”定期运行，设置用户的“等级”（H、M、L）。评级取决于“顾问”拜访“用户”的频率。要求是使预约系统自动化，因此由“模型”进行“临时”预约。 申请将等待确认预约的回复。后续会议等也有同样的情况。希望这足以有所帮助。基本上，在安排约会时，控制在应用程序和用户之间传递多次，
我认为事件驱动模型在这里是最合适的？任何意见表示
感谢
I'm developing an application that I suspect is suitable for using workflow. (It's easy to visualise the physical workflow and tasks between different users.)
My question is what are the advantages to using this method, do you recommend that I go down this route. Is there a better approach.
I've heard mention of a hit in performance? Is this worth considering?
Finally, can anyone recommend a good book which is a good introduction to workflow?
UPDATE:
Brief overview of my solution - In basic terms it's a booking/event/diary system. A 'model' runs periodically which sets the'rating' of the users (H,M,L). Depending on the rating depends how often the 'adviser' visits the 'user'. The requirement is to automate the appointment system, so a 'tentative' appointment is made by the 'model'.
The application will wait for a response confirming the appointment. Same situation with follow up meetings, etc. Hope this is enough to help. Basically control passes between the application and the user several times in arranging appointments
I'm thinking the event driven model would be the most appropriate here? Any input appreciated
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
@Stuart 如果您的应用程序必须遵循一系列离散步骤（工作流程状态），您绝对可以使用 Workflow Foundation (WF) 。您可以将业务流程的流程与应用程序的其他逻辑分开，使其松散耦合，从而更容易修改和增强。
如果您可以简单地决定使用
if-else结构来决定流程是否应移至下一步（状态），则所有步骤都线性遍历，然后顺序工作流程会很好。如果您可以在发生某些事件时从一个步骤移动到另一个步骤，并且可以根据事件直接跳转步骤，那么状态机工作流程就适合您。我已阅读Wrox- Professional Windows Workflow Foundation 由 Todd Kitta 编写。这是一本很好的入门书。您绝对可以在 MSDN 的 Workflow Foundation
@Stuart if your Application has to follow some series of discrete steps (workflow states) you can definitely use Workflow Foundation (WF). You can keep the flow of the business process separate from the other logic of your application making it loosely coupled and thus easier to modify and enhance.
If you can simply decide using
if-elseconstructs to decide if flow should move to next step (state) all the steps are traversed linearly thenSequentialworkflow will be good. If you can move from one step to another on occurrence of some event and can literally jump the steps based on the events thenState Machineworkflow is for you.I've read Wrox- Professional Windows Workflow Foundation authored by Todd Kitta. It is a good book to start with. Definetly you can a wealth of information and examples at home of Workflow Foundation at MSDN