我WF评价为在网络上业务线应用程序的使用，我很想听到这个技术的一些最近的第一手资料。

I am evaluating WF for use in line of business applications on the web, and I would love to hear some recent first-hand accounts of this technology.

在这里，我的主要兴趣是在改善项目中，也许对频繁更改的复杂过程工作时提高开发人员工作效率的可维护性。

My main interest here is in improving the maintainability of projects and maybe in increasing developer productivity when working on complex processes that change frequently.

我真的很喜欢WF的想法，但它似乎是比较陌生的，许多较旧的评论我遇到一提，它的绝大多数复杂，一旦你进入它。

I really like the idea of WF, however it seems to be relatively unknown and many older comments I've come across mention that it's overwhelmingly complex once you get into it.

如果它过度设计到它的不可用的点（或不好的折衷）为小到中等规模的项目，这就是我需要知道的东西。

If it's overdesigned to the point that it's unusable (or a bad tradeoff) for a small to medium-sized project, that's something that I need to know.

当然，它于2006年底被淘汰，所以也许它已经成熟。如果是这样的话，那是另一条信息，这将是非常有益的！

Of course, it has been out since late 2006, so perhaps it has matured. If that's the case, that's another piece of information that would be very helpful!

在此先感谢！

推荐答案

Windows工作流基础是一个非常有能力的产品，但还是非常的第一次版本： - （

Windows Workflow Foundation is a very capable product but still very much in its 1st version :-(

使用的主要原因包括：

在可视化建模业务需求。 从业务规则分离业务逻辑和外化规则的XML文件。 将外部化工作流程为XML文件从分隔条件，你的应用程序的业务流程。 与快速的反应能力，如果没有事情发生的时间有些长一段时间做出反应创建长时间运行的进程。例如发票收不回来。 在长时间运行的工作流程，自动持久性，以资源的使用情况下，让一个进程和/或机器重新启动。 在工作流程帮助业务需求的自动跟踪。

WF是作为一个库/框架，所以大部分的时间，你需要编写实例WF运行时主机。也就是说，使用WCF托管在IIS是一个可行的解决方案，节省了大量的工作。然而，WCF / WF耦合是不完美的，需要一些严肃的工作。看到这里http://msmvps.com/blogs/theproblemsolver/archive/2008/08/06/using-a-transactionscopeactivity-with-a-wcf-receiveactivity.aspx了解更多详情。预计相当多的改变/增强，在未来的版本。

WF comes as a library/framework so most of the time you need to write the host that instantiates the WF runtime. That said, using WCF hosted in IIS is a viable solution and saves a lot of work. However the WCF/WF coupling is less than perfect and needs some serious work. See here http://msmvps.com/blogs/theproblemsolver/archive/2008/08/06/using-a-transactionscopeactivity-with-a-wcf-receiveactivity.aspx for more details. Expect quite a few changes/enhancements in the next version.

WF（和WCF）是pretty的中央来了很多新的东西出来微软。您可以在PDC在期待一些有趣的通知。

WF (and WCF) are pretty central to a lot of the new stuff coming out of Microsoft. You can expect some interesting announcements during the PDC.

BTW保持流程运行多个版本需要一定的工作量，但大多是标准的.NET。我只是做了一系列的从这里开始的主题博客文章：http://msmvps.com/blogs/theproblemsolver/archive/2008/09/10/versioning-long-running-workfows.aspx

BTW keeping multiple versions of a workflow running takes a bit of work but that is mostly standard .NET. I just did a series of blog posts on the subject starting here: http://msmvps.com/blogs/theproblemsolver/archive/2008/09/10/versioning-long-running-workfows.aspx

关于可视化建模业务需求。 在理论上，这工作得很好，意图和执行分离。然而，在实践中，你会下降不少课外活动纯粹出于技术原因的工作流和那种失败的目的是你必须告诉业务分析师忽略一半的形状和线条。

About visually modeling business requirements. In theory this works quite well with a separation of intent and implementation. However in practice you will drop quite a few extra activities on a workflow purely for technical reasons and that sort of defeats the purpose as You have to tell a business analyst to ignore half the shapes and lines.