Asp.net 和 Windows Workflow 是很好的组合吗？
我正在实现一个非常简单的状态机订单处理应用程序。 这是一个有一些变化的电子商务应用程序。 应用程序的用户不会自行编辑工作流程。
微软声称asp.net和Windows Workflow是可以结合的。 安装和维护 asp.net 和 Windows Workflow 的组合有多难？ 我会将工作流状态保留在 sql-server 中。
对我来说，编写自己的状态机代码是否更容易，或者 Windows Workflow 是适合该工作的工具吗？
I am implementing a quite simple state-machine order processing application. It is a e-commerce application with a few twists. The users of the application will not be editing workflows by themselves.
Microsoft claims that asp.net and Windows Workflow is possible to combine. How hard is it to install and maintain a combination of asp.net and Windows Workflow? I would be keeping the workflow state in sql-server.
Is it easier for me to roll my own state machine code or is Windows Workflow the right tool for the job?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
Asp.net 和 WF 相处得很好，而且 WF 不会增加太多维护开销。
这是否适合您的设计很大程度上取决于您的需求。 如果您有很多事件驱动的操作，那么 WF 可能是值得的，否则滚动您自己的跟踪的开销可能会减少系统的复杂性。
WF 相当容易使用，因此我建议制作一个原型并进行试验。
另外，在我看来，根据您的要求，我怀疑 WF 是否是适合您的解决方案。
Asp.net and WF get along just fine, and WF doesn't add much maintenance overhead.
Whether or not this is the right design for you depends a lot on your needs. If you have a lot of event driven actions then WF might be worthwhile, otherwise the overhead of rolling your own tracking would probably add less complexity to the system.
WF is reasonably easy to work with so I'd suggest working up a prototype and experimenting with it.
Also, in my opinion, based on your requirements, I doubt WF would be the right solution for you.
这取决于您的需求。 状态机有多复杂？ 您希望状态机位于何处（例如模型与数据库）？ WWF 提供了一个基于事件的状态机，如果您的状态机嵌入到模型中，这就足够了。
就我个人而言，我已经实现了一个电子商务框架和其他基于工作流程的网站，并且我一直从实现基于数据库的状态机中获得很多乐趣。 总是工作顺利。
另一方面，我的一些同事更喜欢 WWF。
无论如何，它与 ASP.NET 完美配合。
It depends on your needs. How complex is the state machine? Where do you want the state machine to live (e.g. model vs. database)? WWF provides an event based state machine, which is good enough if your state machine is embedded in the model.
Personally I've implemented an e-commerce framework and other workflow based websites and I've have always had a lot of joy from implementing database based state machines. Always worked without a hitch.
On the other hand, some colleagues of mine prefer WWF.
In any case it works perfectly with ASP.NET.
如果你的状态机非常简单，那么我会说你应该自己推出。 你对一切都有更多的控制权。 你可以按照自己的方式处理持久性问题，而不用担心他们是如何做到的。
虽然 WF 看起来确实很酷，但我认为它的强大之处可能在于它很容易将其绑定到 CRM 和 Sharepoint 等框架中。 如果您打算在应用程序中使用这些，那么我肯定会考虑使用 WF。
全面披露：我绝对不是 WF 专家。
If your state machine is very simple, then I would say that you should just roll your own. You have more control over everything. You can deal with persistence on your own terms and not worry about how they do it.
WF does look pretty cool though, but I think that it's power probably lies in the fact that it is easy to tie it into frameworks like CRM and Sharepoint. If you are going to use these in your application, then I would definitely consider using WF.
Full disclosure: I am definitely not a WF expert.