For an introduction to the processes of demand management, see Hitchhiker’s Guide to Demand Management (white paper).
For a sample project that corresponds to the white paper, see Project 2010 Demand Management Sample Project Workflow Solution in the MSDN Code Gallery.
This is good http://projectserverblogs.com/?p=4106
In the Project 2010 SDK download, the Samples\Workflow subdirectory includes the Visual Studio solution for the BranchingWorkflow example and also for the SampleProposal2 solution, which is the source code for the Sample Proposal workflow that is installed with Project Server 2010. The Samples\Workflow\SampleProposal2 subdirectory also includes a flowchart diagram of the workflow stages, phases, and associated project detail pages (PDPs).
Supports only .NET Framework 3.5 for developing Project Server workflows, remote development is not supported.
Development of Project Server workflows with Microsoft SharePoint Designer 2010 is not supported, for the following reasons:
Project Web App sites cannot be opened or modified in SharePoint Designer 2010, because many components on Project Web App pages require programmatic access to project context data and the Project Server Interface (PSI).
All activities in Project Server workflows are wrapped inside the Project Sequence activity, which contains the project context data needed for PSI calls.
SharePoint Designer 2010 does not support string arrays and GUIDs as properties that some Project Server workflow activities require.
Using Visual Studio 2010 to develop and debug Project Server workflows and other solutions for Project Web App requires development on a Project Server computer The Visual Studio 2010 SharePoint Developer Tools connect to a SharePoint instance in many phases of the development process, for example:
Some of the wizards used for creating projects and items access SharePoint configuration information, such as site and list definitions and the Project Server workflow history list.
SharePoint nodes show in the Server explorer, which requires access to SharePoint.
By default, Visual Studio deploys a SharePoint solution package (.wsp file) on a local SharePoint site and activates features for testing.
After activation, Visual Studio attaches to the process for debugging. Activation can be turned off, but testing and debugging require local development.