Beginning Web Development, Silverlight, and ASP.NET AJAX

CHAPTER 9 ■ .NET 3.0: WINDOWS WORKFLOW FOUNDATION 221
Adding a code condition allows you to specify a function that will fire off to evaluate
the condition, and a declarative rule allows you to specify a simple rule. In our case, we’re
just using a very simple rule, so choose this option. Next, notice that the ConditionName
is given a red alert because it isn’t yet set. Change this field to a good name for the rule,
such as ageOver100.
Once you’ve done this, notice that the alert moves to the ConditionExpression field,
as you haven’t yet defined it. Click the ellipsis button (. . .) and the Rule Condition Editor
will open (see Figure 9-9).
Figure 9-9. Adding the rule condition with the editor
Enter the rule this.ageVal > 100, as shown in Figure 9-9. You’ll notice that you have
full IntelliSense, which is a nice touch.
Click OK and the Rule Condition Editor will close, entering the rule into the
Expression property. You’ll also notice that the IfElse node on the Designer now has
no alerts, so it is configured correctly.
Drag a Code activity to the left branch of the IfElse. This is the path that the sequence
will follow if the rule is met (i.e., if the age is over 100). Use the procedures you followed
earlier to add an ExecuteCode function to it, and put this code in that function:
private void codeActivity1_ExecuteCode(object sender, EventArgs e)
{
Console.WriteLine("You say you are " + this.ageVal
+ " years old I don't believe you!");
Console.ReadLine();
}
Repeat this process for the right-hand branch of the IfElse activity. When you get to
the Properties dialog, wire up the ExecuteCode function as before and then add the following
code to it: