Sharepoint Workflows: Designer VS Visual Studio
En un interesante post hacen un analisis comparativo entre las dos herramientas:
|
Category |
SharePoint Designer |
Visual Studio |
|
Supported WF Hosts |
WSS/MOSS |
WSS/MOSS/Others |
|
Development Model |
Wizard based |
Graphical Designer |
|
Types of Workflows Supported |
Sequential |
Sequential and State |
|
Workflow Type |
Markup only; markup file, rules and supporting files are uncompiled |
Markup with code behind compiled into an assembly |
|
Code Behind |
No |
Yes |
|
Activities |
Built-in and use custom |
Built-in, use and develop custom |
|
Forms Technology |
Autogenerated, customizable ASP.NET Forms |
Design forms in any technology including ASP.NET or InfoPath |
|
Association |
Associated automatically with a single list at design time. No other associations possible. |
Can be associated with multiple content types, lists, and document libraries |
|
Initiation |
Initiation forms are supported |
Initiation forms are supported |
|
Modification |
Cannot modify workflow using modification forms |
Can modify workflows |
|
Tasks |
Supports custom task forms |
Supports custom task forms |
|
Deployment |
Automatically deployed to associated list, live changes |
Must build package and deploy workflow using SharePoint feature technology |
|
Debugging |
No Debugging |
Visual Studio Debugging |