Wednesday, July 17, 2013

Difference between SharePoint designer and Visual Studio workflows

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.

No comments:

Post a Comment

Building Secure Azure AI Foundry Agents with Managed Identity

  The credential problem nobody wants to own Every team that connects an Azure AI Foundry agent to Microsoft Graph, SharePoint, Outlook, or...