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

■

Note

One of the tenets of WF development is that workflows are singular, atomic entities. Given this fact, notice

that the workflow class type is explicitly sealed, thereby preventing it from functioning as a parent class for derived

types.

If you now open the related *.Designer.cs file, you will find that InitializeComponent() has set

the Name property accordingly:

partial class ProcessUsernameWorkflow

{

[System.Diagnostics.DebuggerNonUserCode]

private void InitializeComponent()

{

this.Name = "ProcessUsernameWorkflow";

}

}

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

926

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

---

As you make use of the Windows Workflow Toolbox to drag various activities onto the designer

surface and configure them using the Properties window (or the inline smart tags), the *.Designer.

cs file will be updated automatically. Like other IDE-maintained files, you can typically ignore the

code within this file completely and keep focused on authoring code within the primary *.cs file.