I have implented the IDataErrorInfo interface on the BaseEntity class. Thiis interface provides the functionality to offer custom error information that a user interface can bind to. Controls like the DataGridView automatically detect this interface and provide error icons along with descriptions about the error.
Hand in hand with this, I have also added the ability to attach validation rules to the entity objects. There are some built-in validators (StringMaxLength, StringRequired, NotNull, EqualToValue, LessThanOrEqualToValue, etc). There is also a delegate defined that allows you to provide your own validation methods so that you can make you business rule logic as complex as necessary. To add validation rules to your object, you simply need to override the AddValidationRules method (part of BaseEntity). By default, the templates will generate two validation rules for each property (if appropriate): StringMaxLength and NotNull. Each entity now has a property called ValidationRules that provides an AddRule method to add validation rules. You can add as many different rules to each property as you like. Here's the basic AddValidationRules method that is added to the entity class:
protected
{
//Add custom validation rules
The BaseEntity will call any validation rules that were added by the templates. So, how do we add custom validation rules? It's fairly simple (I think...). Let's use the Orders class in Northwind as an example. Let's say that we would like to add the following rules:
- The customer id (CustomerID) must be provided.
- The freight amount (Freight) must be between $0 and $200.
- The order date (OrderDate) must not be in the future.
Let's tackle these one at a time.
1. To implement rule number one, we will use one of the built-in validation methods: StringRequired. We will use the simplest overload for AddRule:
public
ValidationRuleHandler is a delegate defined as:
public
target is the object that is being validated, while e is a ValidationRuleArgs object that contains information about the rule (property to be validate, error description).
To actually add the rule, we use the following syntax:
ValidationRules.AddRule(Validation.
CommonRules.StringRequired, "CustomerID");
The Validation.CommonRules namespace includes several built-in rules to do common validation tasks.
delegateboolValidationRuleHandler(object target, ValidationRuleArgs e) void AddRule(ValidationRuleHandler handler, string propertyName)
2. To implement this rule, we will use two of the built-in validation methods: GreaterThanOrEqualToValue<T> and LessThanOrEqualToValue<T>. These use a slightly different overload of the AddRule method:
public
ValidationRules.AddRule(Validation.
ValidationRules.AddRule(Validation.CommonRules.LessThanOrEqualToValue<Decimal?>, new Validation.CommonRules.CompareValueRuleArgs<Decimal?>("Freight", 200));
3. For this rule, we will use custom validation method called ValidateOrderDate. The only requirement for a validation method is that is must match the ValidationRuleHandler delegate. Here's the code for the custom method:
privatebool ValidateOrderDate(object target, Validation.ValidationRuleArgs e)
{
if (this.OrderDate > DateTime.Today)
{
e.Description = "The Order Date must not be in the future.";
returnfalse;
}
returntrue;
}
There are a couple of things to note here. First, the method needs to return false if the rule is broken or true if the rule is not broken. If the rule is broken, you should set the Description property of the ValidationRuleArgs parameter so that the use gets information about the error.
Here's the complete Orders class to implement all of these rules:
#region Using directives
using System;
using System.ComponentModel;
using System.Collections;
using System.Xml.Serialization;
#endregion
namespace NetTiersTest2.Northwind
{
///<summary>
/// An object representation of the 'Orders' table. [No description found the database]
///</summary>
/// <remarks>
/// This file is generated once and will never be overwritten.
/// </remarks>
publicpartialclassOrders
{
/// <summary>
/// Adds custom validation rules to this object.
/// </summary>
protectedoverridevoid AddValidationRules()
{
base.AddValidationRules();
//Add custom validation rules
ValidationRules.AddRule(Validation.CommonRules.StringRequired, "CustomerID");
ValidationRules.AddRule(Validation.CommonRules.GreaterThanOrEqualToValue<Decimal?>, new Validation.CommonRules.CompareValueRuleArgs<Decimal?>("Freight", 0));
CommonRules.LessThanOrEqualToValue<Decimal?>, new Validation.CommonRules.CompareValueRuleArgs<Decimal?>("Freight", 200));
ValidationRules.AddRule(Validation.
ValidationRules.AddRule(ValidateOrderDate, "OrderDate");
}
privatebool ValidateOrderDate(object target, Validation.ValidationRuleArgs e)
{
if (this.OrderDate > DateTime.Today)
{
e.Description = "The Order Date must not be in the future.";
returnfalse;
}
returntrue;
}
}
}
There are a couple of more properties that are of interest. There is now a property called IsValid that checks the rules to see if any have been broken. You can also get all of the broken rules through the BrokenRulesList property.
Lastly, I will add a couple of disclosures. First, this is not completely integrated into the framework. You should call IsValid prior to saving the object. Second, depending on where Robert goes with the Business layer, this could change significantly. Third, remember that this is a CTP and things may not be perfect!
Send questions and bugs my way... Have a good weekend.
CommonRules.GreaterThanOrEqualToValue<Decimal?>, new Validation.CommonRules.CompareValueRuleArgs<Decimal?>("Freight", 0)); void AddRule(ValidationRuleHandler handler, ValidationRuleArgs args)This overload allows you to pass in a custom ValidationRuleArgs (or sub-class) parameter to pass in additional information to the validator. Heres' the code to add the rule:} overridevoid AddValidationRules()base.AddValidationRules();
转自：http://blog.csdn.net/ilovemsdn/archive/2007/03/27/1543212.aspx