WPF Reflections

Mar 14 2008   4:50PM GMT

Validation



Posted by: MarkWPF
Tags:
Validation
WPF
XAML

There seems to be four ways to go with validation with WPF:

  1. Use IDataErrorInfo
  2. Use custom classes with ValidationRule
  3. Combine 1 and 2
  4. Roll your own

What do I mean by each of these, and why?

  1. Use IDataErrorInfo. You canimplement this interface in your business objects and you get the opportunity to specify validation for each property or for all properties. You do this in (usually) a general purpose method that does validation for all of your properties in your business object. This is good if you need validation for a business object, but not across objects. You can tell wpf to use it (in v3.5) by specifying ValidatesOnDataErrors=”True” in your binding specification.
  2. Inherit a class from ValidationRule, and provide an override for the Validate method. You could do this for either a particular business object, or across a number of objects. You can use it in xaml by specifying it in the binding’s ValidationRules collection.
  3. Do 1 for business object validation, and 2 for any validation that needs to be done across business objects
  4. Do this when you need to extend the validation, e.g. like in the CSLA.Net framework

 Comment on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: