我应该费心学习 Windows 工作流吗？
好的，我已经学习了 WPF 和 WCF，这太棒了。 我没有对 CardSpace 费心，因为它可能不会成功。
我应该为工作流程烦恼吗……值得吗？ 有什么大不了的？
Okay, so I've learned WPF and WCF and that was great. I didn't bother with CardSpace because it's probably not gonna take off.
Should i bother with Workflow,..is it worth it? What's the big deal?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（8）
看过Leon Bambric 关于工作流程软件的帖子吗？
Ever seen Leon Bambric's post on Workflow software?
值得学习或者至少了解WF。 WF 提供了一种不同的应用程序构建范例，这种范例可能在未来成为主流。 进取心？ 是的，也许今天。 但从长远来看，WF 或至少是它所提倡的范例，可能会变得无处不在和普遍。 现在使用工作流来描述程序可能处于 20 年前 OO 和 C++ 的阶段。
学习新事物可以拓宽你的思维。 例如，即使您在日常工作中使用 C# 或 Java，了解 Lisp 也有助于拓宽您解决问题的思路。 国际海事组织。 WF也是一样。
第二个想法是像投资者一样思考。 如果你想提高你作为程序员的价值，是否学习 WF 将取决于你所在的市场或工作。在你的空间或公司中，WF 技能可能值得也可能不值得你付出额外的努力。
It is worth learning or at least understanding WF. WF offers a different paradigm for building apps, a paradigm which may become mainstream in the future. Enterprisey? Yes, maybe today. But longer term WF or at least the paradigm it promotes, may become ubiquitous and universal. Using Workflows to describe programs may today be in the stage where OO and C++ was, 20 years ago.
Learning a new thing broadens your thinking. For example, even if you use C# or Java in your day-to-day job, knowing Lisp helps broaden your thinking about how to solve problems. IMO. WF is the same.
A second thought is to think like an investor. If you want to raise the value of YOU as a programmer, whether to learn WF would depend on the market or job you are in. WF skills in your space or in your company may or may not be worth your extra effort.
Windows 工作流对于多种不同类型的应用程序很有用。 如果您不会编写其中之一，则无需费心学习它。
但如果你不需要这些，为什么还要麻烦呢？ 只需阅读一些白皮书，或观看一些视频，看看其中是否有任何有趣的内容。
一件有趣但不明显的事情是：工作流设计器和规则设计器都可以托管在任意 Windows 窗体应用程序中。 这允许它们在您自己的应用程序中重用，例如，如果您需要一种自定义条件处理的方法。
Windows Workflow is useful for several different kinds of application. If you're not writing one of them, then there's no need to bother learning it.
But if you don't need any of this, why bother? Just read some of the whitepapers, or look at some of the videos and see if any of it looks interesting.
One interesting thing that's not obvious: both the workflow designer and the rules designer can be hosted in arbitrary Windows Forms applications. This allows them to be reused in your own application, if, for instance, you need a way to customize conditional processing.
我认为对当前 Windows 工作流程的普遍共识是该产品尚未完全准备好迎接黄金时段。 如果您想使用当前框架完成一些不那么简单的事情，您可能需要编写一些自定义任务来填补功能空白。 当工作流程的复杂性开始堆积时，我也遇到了设计师崩溃的问题。
根据我听到/读到的有关 Windows Workflow 的信息，下一版本 (v4.0) 是完全重写，修复了当前版本中的许多问题。 他们声称向后兼容 v3/3.5 工作流程，但您可能必须非常了解该框架才能知道发生了什么变化以及如果它不能立即工作如何修复它。
除非您现在有一个项目绝对需要此功能，否则您最好等到新版本发布。
I think the general consensus on the current Windows Workflow is that the product is not quite ready for primetime yet. If you want to get anything more than trivial accomplished with the current framework, you will likely have to write a few custom tasks to fill in functionality gaps. I've also had issues with the designer flaking out when the complexity of the workflow starts piling up.
From what I've been hearing/reading about Windows Workflow, the next version (v4.0) is a complete rewrite that fixes a lot of the issues in the current version. They claim backward compatibility with v3/3.5 workflows, but you probably will have to know the framework pretty well to know what changed and how to fix it if it doesn't work right away.
Unless you have a project that absolutely demands this functionality today, you're probably better off waiting until the new bits ship.
就像保罗说的，这取决于你工作的环境。就我个人而言，因为我永远不知道生活会带我去哪里（公司发展、创业等），所以当我有机会时，我会尽力学习一切。
我的建议是，如果你有时间、直觉和开发环境……学习它。 你永远不知道它什么时候会派上用场。
Like Paul said, it depends on the environment you work in. Personally, since I never know where life is going to take me (corporate development, startup, etc.) I try to learn everything I can when I have the chance.
My advice would be, if you have the time, the intuition, and the development environment...learn it. You never know when it might come in handy at some point down the road.
感谢所有提供意见的人。 Cheeso 得到了答案，因为他获得了最多的选票，但所有意见都会受到赞赏。 我想我会采纳 Scroll Lock 的建议，等到 v4.0 后再认真看一下。
Thanks for all the advice guys. Cheeso get's the answer since he got the most up votes but all opinions are appreciated. I think I'll take Scroll Lock's advice and wait until v4.0 until I take a serious look.
我最初真的很喜欢工作流的概念，但最终我想我只会使用无状态之类的东西或滚动我自己的状态机，并使用数据库进行持久化。 我现在最大的问题是工作流程运行时似乎仍然存在巨大的内存泄漏。 让我有点紧张。
I originally really liked the concept of workflows, but in the end I think I'll just use something like stateless or roll my own statemachine, and use a database for persistence. My biggest issue with it right now is that there still seems to be a huge memory leak in the workflow runtime. Makes me kind of nervous.
这取决于您构建的软件类型。 WPF 很简洁。 WCF 有其用途。 不过，Windows 工作流非常“企业化”。 它需要更多设置并且可能会变得复杂。
除非您构建的企业软件可以从可定义的工作流程中受益，否则我不会太在意它。
It depends on the type of software you build. WPF is neat. WCF has its uses. Windows Workflow is pretty "enterprisey", though. It requires more setup and can get complex.
Unless you build enterprise software that would benefit from a definable workflow, I wouldn't bother much with it.