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

// Now, create a WF instance that represents our type.

WorkflowInstance instance =

workflowRuntime.CreateWorkflow(typeof(UserDataWFApp.ProcessUsernameWorkflow));

instance.Start();

waitHandle.WaitOne();

}

}

First of all, notice that the WorkflowCompleted and WorkflowTerminated events of

WorkflowRuntime are handled using C# anonymous method syntax. The WorkflowCompleted event

fires when the WF engine has completed executing a workflow instance, while WorkflowTerminated

fires if the engine terminates with an error.

Strictly speaking, you are not required to handle these events, although the IDE-generated

code does so in order to inform the waiting thread these events have occurred using the

AutoResetEvent type. This is especially important for a console-based application, as the WF engine

is operating on a secondary thread of execution. If the workflow logic did not make use of some sort

of wait handle, the main thread might terminate before the WF instance was able to perform its

work.

The next point of interest regarding the code within Main() is the creation of the

WorkflowInstance type. Notice that the WorkflowRuntime type exposes a method named

CreateWorkflow(), which expects type information representing the workflow to be created. At this

point, we simply call Start() from the returned object reference. This is all that is required to fire up

the WF runtime engine and begin the processing of our custom workflow.