Is there a technical reason why ValidationRule is not a DependencyObject?
Is there a technical reason why ValidationRule is not a DependencyObject ?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there a technical reason why ValidationRule is not a DependencyObject?
Unfortunately in WPF who you derive from is often the difference between something that just works and something that is totally useless. But in general, the class designers want to pick the least possible base class that they needed. There’s really no reason that ValidationRule needs to be tied to WPF at all other than the fact that it’s defined in a WPF assembly. But as we’re finding out, that makes it quite painful to do what you’re trying to do.