Validation component is a good way to avoid some predictable exceptions which come from wrong inputs and cause unexpected state for your application. Using validator component you can avoid these exceptions and give appropriate error texts before compilation to correct your input parameters.
Adding a validator component to a custom workflow is very simple and consists of two steps:
- Create a validator component for custom activity by inheriting from ActivityValidator base class.
- Add an ActivityValidator attribute to custom workflow class.
Ok, most things will be done in first step.
There is a ActivityValidator class in System.Workflow.ComponentModel.Compiler. To build a validator you need to create a new class and derive it from this base class and override its Validate() method. Validate() returns a ValidationErrorCollection object which consists of all validation errors for the activity. This method also has two parameters: a ValidationManager and an object. Later you can use this second parameter (object) to convert it to the type of your custom activity and get access to your activity components.
I want to extend the custom workflow activity that I used in my previous post to validate its Path property and use a regular expression to make sure user enters a valid path with .txt file extension.
I add a CustomActivityValidator class to my Class Library project (created in my previous post) and derive it from ActivityValidator then override Validate() method. After that I convert object parameter to my custom activity type (named CustomActivity) and use this newly created object to get access to its Path property and validate its value. In next step I use a regular expression to check if given Path property is valid otherwise I add a new ValidationError to my ValidationErrorCollection and finally returns this ValidationErrorCollection.
using System;
using System.Text.RegularExpressions;
using System.Workflow.ComponentModel.Compiler;
namespace CustomActivitySample
{
internal sealed class CustomActivityValidator : ActivityValidator
{
public override ValidationErrorCollection Validate(ValidationManager manager, object obj)
{
CustomActivity customActivity = obj as CustomActivity;
ValidationErrorCollection errorCollection = new ValidationErrorCollection();
if (customActivity != null)
{
// Regular Expression inspired from Steve’s RegExLib.Com
Regex regEx = new Regex(“([a-zA-Z]:(\\w+)*\\[a-zA-Z0_9]+)?.txt”,
RegexOptions.IgnoreCase | RegexOptions.Multiline);
if (!regEx.IsMatch(customActivity.Path))
errorCollection.Add(new ValidationError
(“String value provided for Path property is not valid!”, 1984));
}
return errorCollection;
}
}
}
Now that I have a validator component in hand, I can simply add an ActivityValidator attribute to my custom workflow class and pass the type of this validator class to it. Do not forget to add a reference to System.Workflow.ComponentModel.Compiler before adding this attribute.
using System;
using System.Collections.Generic;
using System.Text;
using System.Workflow;
using System.Workflow.Activities;
using System.Workflow.Runtime;
using System.Workflow.ComponentModel;
using System.Workflow.ComponentModel.Design;
using System.IO;
using System.Workflow.ComponentModel.Compiler;
namespace CustomActivitySample
{
[ActivityValidator(typeof(CustomActivityValidator))]
public class CustomActivity : Activity
{
Alright, now my custom activity has a validator component and I can test it. After compiling this custom activity to an assembly and replacing my previous custom activity in Toolbox with this new one and add it to a Sequential Workflow, I can set its properties.
If I put an invalid value for Path property (for example a path with .jpg extension), I can see that an error icon appears on top right corner of my activity. If I click on it then it shows an error text (provided in validator component code).
It also shows this error in Error List window.
Heh, do you want to escape and build?! Just do that to see what will happen!
Articolo preso dal seguente link:
http://nayyeri.net/blog/how-to-write-a-validator-for-custom-workflow-activity/
