Working with Custom Validators using Enterprise Library 3: ASP Alliance

Print Add To Favorites Email To Friend Rate This Article
Working with Custom Validators using Enterprise Library 3

page 6 of 8

by Brian Mains
Feedback

Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 32595/ 50

Article Contents:

Other Considerations

In the custom code I created, I disregarded most of the base class constructors, which pass in a message template that overrides the default, a tag, or a negated property determining whether it is looking at the opposite results. I disregarded it because it I had no need for it in this example, but if I was building my own custom validation for a framework or library, I would have included additional constructor overloads to incorporate this information.

« (Page 5)

View Entire Article

(Page 7) »

User Comments

Title: mmm Reply
Name: Brian
Date: 2008-06-23 10:46:18 AM
Comment:
Validator doesn't inherit from that class, correct. You have to create an accompying attribute that works along side of it. Create another class that inherits from ValidatorAttribute (the attribute class). It has a method you need to override that uses your validator to validate the data. Sorry, I didn't include it in the article.

Title: mmm
Name: John
Date: 2008-06-21 11:58:45 PM
Comment:
Base class Validator don't inherit System.Attribute. How can i use it in this way:
[StringLengthValidator(7, RangeBoundaryType.Inclusive, 150,
RangeBoundaryType.Inclusive,
"The email address must be between 7 and 150 characters",
Ruleset = "primary")
, ContainsCharactersValidator("@.", ContainsCharacters.All,
"The email must have an @ and at least one period",
Ruleset = "primary"),
EmailDomainValidator(".com", ".net", ".edu", ".gov", ".biz", ".tv",
Ruleset =
"primary")]
????

Product Spotlight