Now a lot of people are using SharePoint in the job stream,
SharePoint in the 07 era there are only two ways to develop workflows, one is to take advantage of SharePoint Designer to do without code development workflow,
Another is to exploit the VS development code workflow.
These two types of workflow development, for the lack of WF development experience, it is recommended to use the designer development workflow.
Adding a Visio graphical workflow to SharePoint 2010 adds nothing to your personal feeling. It's a total waste of time.
The SharePoint workflow engine uses Windows Workflow Foundation
So SharePoint workflows support both sequential and state machine workflows.
The sequential workflow is very well understood, that is, from top to bottom, a line to solve the problem. The state machine workflow is relatively complex,
This is also a reason to discourage many developers, but if your workflow needs to return to such an operation, you must use the volume, which is unavoidable.
In order to make it popular with Microsoft technology, I decided to sacrifice some of my time to introduce the SharePoint workflow solution,
The content is simple, and there is no very complicated workflow, just to introduce some knowledge points.
Specific content
1. Creating and debugging a SharePoint workflow solution
2. Create a workflow with an associated form and a startup form
3. Add an application page to the workflow
4. Create a custom site workflow activity
5. Import SharePoint Designer reusable workflows into Visual Studio
6. State Machine Workflow Development Introduction
7. A simple state machine workflow instance
8. Developing a returnable state machine workflow
9. The applicant custom multilevel approver workflow in the list form
10. What does this say? I do not know, in order to gather 10 of Ah, want to know what?
All of the above are developed using SharePoint + VS 2010, and the project type is SharePoint 2010 project.