Visual Studio 2008 provides lot of workflow templates. if you see the screen , two of those belong to Sharepoint.
1. SharePoint 2007 Sequential Workflow
2. SharePoint 2007 State Machine Workflow
Sequential workflow represents a workflow as a sequence of steps that must be executed in order until the last activity is completed. A state machine workflow represents a set of states, transitions, and actions. One state is denoted as the start state, and then, based on an event, a transition can be made to another state. Below is a typical example of a Sequential workflow.
2. SharePoint 2007 State Machine Workflow
Sequential workflow represents a workflow as a sequence of steps that must be executed in order until the last activity is completed. A state machine workflow represents a set of states, transitions, and actions. One state is denoted as the start state, and then, based on an event, a transition can be made to another state. Below is a typical example of a Sequential workflow.
.png)
when you select any of these workflow template, it executes the workflow wizard that allows to do debugging on the workflows on sharepoint that requires special permissions. for e.g this wizard takes care of deploying workflow customization on Global Assembly Cache (GAC). Wizard also takes care of associating the workflow template with a document library or list. It how an instance of your workflow can be started. Without VSTO you need to handle this outside of Visual Studio in separate steps. Really i would say that with lots of inclusion of sharepoint related work in Visual Studio, Microsoft is really making the life ease of the developers.
1 comment:
Hi Nithin,
This is really good but this only works on 32 bit OS, what shuould be the approach for building visual studio 2008 workflows on a 64 bit OS.
thank you
Prasad
Post a Comment