Workflow Development Tools Comparison
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
The following table offers a detailed comparison between the capabilities offered by the Visual Studio 2005 Designer for Windows Workflow Foundation and Office SharePoint Designer 2007, and the workflows you can create with each.
Visual Studio 2005 Designer for Windows Workflow Foundation |
Office SharePoint Designer 2007 |
Can write workflows for Windows SharePoint Services 3.0 |
Can write workflows for Windows SharePoint Services 3.0 |
Code-behind file enables developer to write custom Microsoft Visual C# or Microsoft Visual Basic code to express business logic |
No code behind; workflow rules file declaratively encapsulates business logic instead |
Generates workflow markup file |
Generates workflow markup file |
Workflow is authored as a template, which can be associated with multiple sites and lists |
Workflow is authored against and data-bound to specific list at design time |
Workflow markup file, or markup and code-behind files, compiled into workflow assembly |
Workflow markup, workflow rules, and supporting file are stored, uncompiled, in a specific document library on the site |
Workflow template must be associated with each list on which it is to be available. |
Association happens when the workflow is authored against the specific list; no later association is necessary or possible |
Workflow template can be associated with a site content type. |
Cannot author workflows against content types. |
Can use any forms technology. For example, Microsoft ASP.NET 2.0 forms for Windows SharePoint Services 3.0 workflows. |
Automatically generates Microsoft ASP.NET 2.0 forms, which you can then customize. |
Can include workflow modifications |
Workflow modifications are not available |
Can author custom activities for inclusion in workflows |
Must use activities provided |
Package workflow assembly and workflow definition as a SharePoint Feature, and deploy to the site |
Automatically handles deployment to specific list |
Can use Initiation form to gather information from the user when they start the workflow |
Can use Initiation form to gather information from the user when they start the workflow |
Can use custom forms for users to interact with tasks in Windows SharePoint Services 3.0 |
Can use custom forms for users to interact with SharePoint tasks |
Visual Studio debugging available |
No step-by-step debugging available |
Can author both sequential and state workflows |
Can author only sequential workflows |
See Also
Concepts
Workflow Development for Windows SharePoint Services