1) Download and extract the presentation Zip file (WF Presentation. zip).
Note: Extract to the c:\ drive to install to a folder called:
C:\WF Presentation

2) If you have not already set up your development environment for Windows Workflow Foundation,  Please read the below post for instructions on how to do so.
http://objectsharp.com/cs/blogs/matt/archive/2007/03/24/follow-up-to-fundamentals-of-wf-presentation-and-developer-resources-for-wf.aspx

3) To run Demo1 you must first set up the SqlPersistence Database.
You must have a access to a Sql Instance where you can create a new 
database.

For detailed instructions on how to do this, navigate to the below link:
http://msdn2.microsoft.com/en-us/library/aa349366.aspx
BUT:
Abbreviated instructions are as below. By doing the below, the demo will work:

a) Using SQL Server 2005, SQL Server 2000 or later versions, or SQL Server 2000 Desktop Engine (MSDE),  
create a new database named WorkflowPersistenceStore by using the SQL query statement:

 
CREATE DATABASE WorkflowPersistenceStore


b) In the SQL Query Analyzer workspace, select the database that you created in step a) from the list  
of available databases.

c) On the File menu, click Open, and then open the SQL script  
%WINDIR%\Microsoft.NET\Framework\v3.0\Windows Workflow  
Foundation\SQL\<language>\SqlPersistence_Schema.

d) Run the query by clicking Execute, or by pressing F5 to create the SQL Persistence Service tables.

e) On the File menu, click Open, and then open the SQL script  
%WINDIR%\Microsoft.NET\Framework\v3.0\Windows Workflow Foundation\SQL\<language>\SqlPersistence_Logic.

f) Run the query by clicking Execute, or by pressing F5 to create the SQL Persistence Service stored  
procedures.

Open up C:\WF Presentation\Demo1\Demo1.sln in Visual Studio 2005.

In the SecondWorkflow project, open up the App.config table. Ensure that 
connectionString is pointing to your SqlPersistence database.

Place Breakpoints in the code or the designer for Workflow1.
Press F5 to run the demo.

A console application will be launched that will host the workflow and output Console.Writelines from the code.

4) To run Demo2. Open up solution:
C:\WF Presentation\Demo2\Demo2.sln

Right mouse button on the BugStateMachine project and navigate to the Debug Section:

Ensure that the Start External Program is set to your copy of the TestWorkFlow.exe.
If you unzipped to the c:\ drive it should be set to:
C:\WF Presentation\Demo2\TestWorkFlow\bin\Debug\TestWorkFlow.exe 

Also ensure that the BugStateMachine project is set to the start up project.

Open up the BugDemoWorkflowSM workflow project in the BugStateMachine project.
Place breakpoints on the four State Activities.

Press F5 to run, the TestWorkflow Windows app should be launched. 

When the window is launched, enter a Bug Id and then press the Start State Machine Instance button.
The breakpoints in the Workflow should be hit. Keep pressing F5 until all the breakpoints 
have been exhausted.

Select the newly added row in the Windows gird and then press the DevBugFixed button.
The State should be transitioned to the TesterProcessBugState. 

Experiment with pressing different buttons. If you get an error as something like the below:

An unhandled exception of type 'System.Workflow.Activities.EventDeliveryFailedException' occurred in  
System.Workflow.Activities.dll
Additional information: Event "DevelopmentBugFixed" on interface type "BugLocalServices.IBugService"  
for instance id "c5fe310e-e2c5-4bff-b490-b46423744922" cannot be delivered.

It means that a illegal event was raised.
For example if the StateMachine is currently set to the TesterProcessBugState and you pressed
the DevBugFixed button, the above error will appear.
i.e. The DevelopmentBugFixed event was raised in the TesterProcessBugState Activity that 
is not set up to handle this event.

5) Demo3. 
I do not have any specific intructions on how to set up this simple demo, but 
you will need BizTalk 2006 installed on your machine to get it to work. The basic flow of this demo  
is:

a) BizTalk Orchestration that accepts an incoming PO is exposed as a Web Service
b) Workflow will call the exposed Web service, that will pass the PO to the 
Biztalk Orchestration and send Ack back to the workflow.