Sharepoint 工作流程与 Windows 工作流程
我们正在实施 sharepoint 应用程序，我们想了解 SharePoint 工作流与 Windows 工作流的优缺点。
We are in the process of implementing the sharepoint application, we would like to know the the pros and cons of SharePoint workflow versus Windows workflow.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
SharePoint 中的工作流是使用 Windows Workflow Foundation 实现的，因此它们并没有那么不同，但有关该实现的一些事项仍然需要注意。
SharePoint 是一个 Windows 工作流主机，因此您不必实现自己的主机，如果您同意 SharePoint 团队做出的决定，那就没问题：
如果这些选择符合您的喜好，那么请务必使用 SharePoint 工作流。
如果没有，则实施您自己的主机并做出您自己的决定。
Workflows in SharePoint are implemented using the Windows Workflow Foundation, so they are not that different, but there still are some things to be aware of regarding that implementation.
SharePoint is a Windows Workflow host, so you don't have to implement your own host which is fine if you agree with the decisions made by the SharePoint team:
If these choices are to your liking then by all means use the SharePoint workflows.
If not then implement your own host and make your own decisions.
它们是同一件事。当前的 Windows 工作流引擎是为 SharePoint 创建的。
现在应该注意的是，工作流引擎将随着 .Net 4.0 的发布而进行彻底修改。我不知道具体细节，但我听说差异很大。我假设这将在 Sharepoint 2010 中使用，但我没有任何相关信息。
这是 链接 描述 4.0 中的升级。
They are the same thing. The current Windows Workflow Engine was created for SharePoint.
Now it should be noted, that the Workflow engine is going to be overhauled with the release of .Net 4.0. I don't know the specifics, but I've been told the differences are significant. I woudld assume this is going to be used in Sharepoint 2010, but I don't have any information on that.
Here is a link describing the upgrade in 4.0.
您尚未指定是在 SharePoint 中构建自定义编码应用程序还是通过浏览器配置开箱即用的解决方案。无论哪种方式，下面都是 SharePoint 中工作流的一些选项。
我在易用性方面找到了最佳平衡开发和功能的重点是尝试按照我提供的顺序完成上面的列表，并且只有在您肯定无法实现当前点的要求时才前进到下一个选项。
You haven’t specified whether you’re building a custom coded application in SharePoint or configuring an out of the box solution via the browser. Either way, here are a few options for workflows in SharePoint.
I find the best balance in terms of ease of development and functionality is to try and work through the above list in the order I provided them and only progress to the next option if you definitely can’t implement the requirement with the current point.
基本上是相同的技术。如果您知道其中一个，您可以轻松使用/切换到另一个。
当您将 SharePoint dll 添加到解决方案时，您将获得一些可以在工作流程中使用的特定 SharePoint“活动”。 （创建任务，...）
您的 SharePoint Server 将充当工作流的主机。
在 SharePoint 中部署工作流的最佳方法是使用 SharePoint 功能。这告诉 SharePoint 要使用哪些 dll（程序集）以及要显示哪些（输入）页面。
作为输入页面，您可以使用简单的 .net aspx 页面或 infopath 表单。两者都需要一些尝试和错误才能掌握窍门。
It's basically the same technology. If you know one you can easily work with / switch to the other.
When you add the SharePoint dll to your solution you get some specific SharePoint 'activities' that you can use in your workflow. (create task, ...)
Your SharePoint Server will act as a host for your workflows.
The best way to deploy a workflow in SharePoint is by using a SharePoint feature. This tells SharePoint what dll (assemblies) to use and which (input) pages to show.
As input pages you can use simple .net aspx pages or infopath forms. Both require some trial and error to get the hang of it.
SharePoint 仅使用 Windows Workflow Foundation (WF) 作为其工作流引擎。 WF 本身只是一个通用的工作流引擎。
为了使用 WF，您必须实现一个主机进程来执行工作流，并对其进行配置，以便将实例保存到数据库等（现在大多数人使用 WCF 服务作为工作流主机，请参阅 此处 或 此处）。
SharePoint 附带了所有已配置的内容，并实现了自己的工作流主机，因此您可以开始使用开箱即用的工作流。除此之外，它还附带自定义活动和其他特定于 SharePoint 的好东西。
SharePoint simply uses windows workflow Foundation (WF) as its workflow engine. WF in itself is just a generic workflow engine.
In order to use WF you must implement a host process for the execution of workflows, and configure it so it persists instances to database etc (these days most people use a WCF service as a workflow host, see here or here).
SharePoint comes with everything already configured and implements its own workflow host, so you can start using workflows out of the box. Apart from that, it comes with custom activities and other goodies specific to SharePoint.
正如其他答案中所述，它们是相同的，因为它们使用 Windows WOrkflow Foundation。话虽这么说，当谈到通过 SharePOint Designer 创建的工作流时，需要记住一件重要的事情：它们不是开箱即用的“可移植”的，这意味着您可以创建一个绑定到列表 a 的工作流，然后将列表另存为模板，然后基于该模板创建另一个列表，工作流程将无法工作（您已重新绑定它，因为它仍然引用原始列表的 id (guid)。
As stated in other answers, they are the same, as they use the Windows WOrkflow Foundation. That being said, there is a major thing to keep in mind when it comes to Workflows created through SharePOint Designer: They are not "portable" out of the box, meaning that you can create one bound to list a, then save the list as a template and then create another list based on that template, the workflow will NOT work (you have rebind it as it is still referencing the original list's id (guid).