Datasheet

Chapter 1: Workfl ow Programming Principles
39
key.snk: This is the key file that is used to sign the assembly. As you can see, Visual Studio
always compiles the workflow code - behind class into a strong - named assembly. Every time you
build this project, Visual Studio automatically compiles the workflow into a strong - named
assembly and installs this assembly in the global assembly cache (GAC). As you ’ ll see later in
this book, SharePoint expects the workflow code - behind class to be compiled into a strong -
named assembly and installed in the GAC.
Workflow1.cs: This file contains the first portion of the workflow code - behind class. Keep in
mind that the workflow code - behind class in this file is defined as a partial class.
Workflow1.designer.cs: This file contains the second portion of the workflow code - behind class.
❑
❑
❑
Figure 1-6
Figure 1-7
Now go ahead and delete the Workflow1.designer.cs file and replace the contents of the Workflow1.cs
file with Listing 1 - 12 , earlier in this chapter. Add the following files to the project:
CustomConditions.cs: Add Listing 1 - 11 to this file.
SequenceActivity.cs: Add Listing 1 - 7 to this file.
WhileActivity.cs: Add Listing 1 - 9 to this file.
The Solution Explorer should now look like Figure 1 - 7 .
❑
❑
❑
c01.indd 39c01.indd 39 8/25/08 4:03:03 PM8/25/08 4:03:03 PM