Difference between SharePoint designer and Visual Studio workflows

In this post we will discuss about what is the differnce between SharePoint designer and Visual Studio workflows.

You can also check: Sequential vs State machine workflows in SharePoint 2010, Disposing SharePoint Objects and Creating Multiple Tasks from a SharePoint 2010 Workflow.

Below are some differences between SharePoint designer workflows and Visual Studio workflows.

SharePoint Designer:

- SharePoint Designer is a code-free environment.

- Through designer we can make Sequential workflows only.

- Workflows created by designer can be deployed across a site collection only not beyond that.

- These workflows automatically deployed into SharePoint.

- Visio can be used to model workflow logic.

- But no debugging available to step through a workflow at runtime.

- Intuitive support for forms customization.

- Workflows cannot be modified at runtime.

- Compiled just-in-time.

Visual Studio:
- Code-centric development

- Visual studio workflows supports both sequential and state machines.

- These workflows deployable across entire farm via a feature.

- Must be packaged within a feature and deployed by a farm administrator or in a sandbox.

- No support for Visio.

- Full debugging experience available.

- Less intuitive InfoPath integration. Availability for ASP.NET custom forms.

- Workflows can be modified while running.

- Compiled at design time.