Workflows: Comparing the Visual Studio Designer for Windows Workflow Foundation and SharePoint Designer 2007

The following sections offer a detailed comparison between the capabilities offered by the Visual Studio Designer for Windows Workflow Foundation and Office SharePoint Designer 2007, and the workflows you can create with each.

Visual Studio 2005 Designer

• Can write workflows for Windows SharePoint Services or SharePoint Server
• Code-behind file enables developer to write custom Visual C# or Visual Basic .NET code to express business logic
• Generates workflow markup file
• Workflow is authored as a template, which can be associated with multiple sites and lists
• Workflow markup file, or markup and code-behind files, are compiled into workflow assembly
• Workflow template must be associated with each list on which it is to be available
• Can use any forms technology. For example, ASP forms for Windows SharePoint Services workflows, or InfoPath forms for SharePoint Server workflows
• Can include workflow modifications
• Can use custom symmetrical InfoPath forms, which enables Office client integration of custom workflow forms
• Can author custom activities for inclusion in workflows
• Package workflow assembly and workflow definition as a SharePoint feature, and deploy to the site
• Can use Initiation form to gather information from the user when starting the workflow
• Can use custom forms for users to interact with SharePoint tasks
• Visual Studio debugging available
• Can author both sequential and state workflows

SharePoint Designer 2007

• Can write workflows for Windows SharePoint Services or SharePoint Server
• No code-behind file; workflow rules file declaratively encapsulates business logic
• Generates workflow markup file
• Workflow is authored against and data-bound to specific list at design time
• Workflow markup, workflow rules, and supporting file are stored, uncompiled, in a specific document library on the site
• Association happens when the workflow is authored against the specific list; no later association is necessary or possible
• Automatically generates ASP.NET forms, which you can then customize
• Workflow modifications are not available
• InfoPath forms integration not available
• Must use activities provided
• Automatically handles deployment to specific list
• Can use Initiation form to gather information from the user when starting the workflow
• Can use custom forms for users to interact with SharePoint tasks
• No step-by-step debugging available
• Can author only sequential workflows