微软工作流基础真的有用吗？
今天，我进行了《微软工作流基础》的培训。
虽然我认为这个想法很巧妙，但我仍然将其视为概念验证，而不是现实生活中的解决方案。构建整个应用程序而无需键入一行代码（或仅其中几行代码）似乎是错误的。
您是否曾经使用过这项技术？如果使用过，它真的适合大公司项目吗？使用它有什么缺点/优点？
Today, I had a training on "Microsoft Workflow Foundation".
While I think the idea is neat, I still see it as a Proof Of Concept and not as a real-life solution. Building an entire application without having to type a single line of code (or only a few of them) seems just wrong.
Have you ever used this technology and if so, can it really fit to big company projects ? What drawbacks/advantages have you got using it ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我不认为它会取代整个应用程序，但更可能在应用程序的架构中使用，以使其更易于维护和构建，因为业务逻辑是分离出来的。
在我之前构建的应用程序中，我们使用自己的工作流程解决方案来使我们的网站更易于维护，并且可以快速添加新内容和控件，而无需重新编译和控制。重新部署。
即使是小型应用，MWF 也绝对可以占有一席之地，具体取决于它的需求。
I don't see it replacing an entire application, but more likely used in the architecture of an application to make it easier to maintain and build, since business logic is separated out.
In previous application I've built, we used our own workflow solution to make our site easier to maintain and also to add new content and controls quickly without recompiling & redeploying.
MWF can definitely have a place in even small applications, depending on it's needs.
工作流只是较大应用程序的一部分，就像您的整个应用程序不是 WPF 或 ADO 一样。而且它确实在实际应用中得到了使用并且非常有用。需要寻找合适的项目是在应用程序中充当小项目的项目，例如销售订单、雇用新人或建造房屋。所有这些都有一个开始，经历多个步骤，有一个结束，您可能会在您的应用程序中管理多个步骤。描述一个或多个工作流程中的“项目”步骤，并为每次发生启动一个步骤。
由于这种情况很常见，我相信更多的开发人员可以从在应用程序中使用工作流中受益。
Workflow is just a part of a larger application, just like your entire app isn't WPF or ADO. And it is certainly used in real applications and very useful. Things to look for where it is a good fit are items that behave as small projects in an applications like a sales orders, hiring a new person or building a house. All thee have a start, go through multiple steps, have an ending and you are likely to manage multiple in your application. Describe the "project" steps in one or more workflows and start one for each occurrence.
As this is a very common occurrence I believe far more developers could benefit from using workflow in their applications.
最近，我一直在使用它来替换代码库中那些在分支和循环逻辑方面确实很混乱的部分。当您可以在图片中可视化这些内容，并且只需创建一些自定义活动来执行您的逻辑时，就可以更轻松地准确了解正在发生的情况。
整个应用程序没有重写，例如，确实没有理由使用工作流执行任何 CRUD 类型操作，但它对于某些“繁重”操作非常有帮助。
Lately I've been using it to replace those parts of the codebase that are really messy as far as the branching and looping logic is concerned. When you can visualize that stuff in a picture, and just create some custom activities to perform your logic, it makes knowing exactly what is going on much easier.
The entire application wasn't rewritten, for example there's really no reason to do any CRUD type operations with workflow, but its been very helpful for some of the "heavy lifting" operations.