This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

■

I N T R O D U C I N G   W I N D O W S   W O R K F L O W   F O U N D AT I O N

948

8849CH26.qxd  10/10/07  11:46 AM  Page 948

---

Figure 26-26.

The completed Sequential Workflow Library project 

Figure 26-27.

Building a Windows Forms Application project to test our workflow library

C H A P T E R   2 6  

■

I N T R O D U C I N G   W I N D O W S   W O R K F L O W   F O U N D AT I O N

949

8849CH26.qxd  10/10/07  11:46 AM  Page 949

---

Once you have done so, rename your initial Form1.cs file to the more fitting MainForm.cs by

right-clicking the Form1.cs icon in Solution Explorer and selecting the Rename option. Next, add a

reference to each of the following .NET assemblies:

• CreditCheckWFLib.dll

• System.Workflow.Runtime.dll

• System.Workflow.Activities.dll

• System.Workflow.ComponentModel.dll

The user interface of our application will consist of a descriptive Label, a TextBox (named

txtCustomerID), and a single Button type (named btnExecuteWorkflow) on the initial form. 

Figure 26-28 shows one possible design.

Figure 26-28.

A simple UI to test our workflow library

Once you place these UI elements on the designer, handle the Click event of the Button type by

double-clicking the button icon located on the designer surface. 

Within your code file, implement the Click event handler to fire up the WF runtime engine and

create an instance of your custom workflow. Notice that the following code is identical to that found

within a console-based workflow application (minus the threading code required to keep the con-

sole program alive until the workflow completes):