MS Enterprise Library validation problem -
I have a problem with the Microsoft Enterprise Library recognition framework.
Say we have datetime? Farm. When using NotNullValidator with another validator (we say, day-time validator) I always go into an exception.
The scenario is: I pass a blank value NotNullValidator works fine (this determines the verification problem) but then another vendor throws a NullReferenceException, and trying to implement its rules is.
I have tried that with a CompositeValidator and logic, if the first verifier has reported a problem, the following assumptions will be ignored (as should be with an argument) but my There is no luck at all.
How could it be possible to co-create NotNullValidator with other validators, first of all to each other (obviously)?
The above is not currently possible. Unfortunately, the composite validator does not do short circuits.
If you need to do this then I will just write a custom verifier, quick and relatively painless.
Comments
Post a Comment