The text of this article is not in this database — only its details are. The old site it was published on is gone, but the Internet Archive kept a copy: 16 steps to write flexible business validation in C# using Validation Blocks
Join the conversation! Your thoughts help the community grow.
Sign in to leave a comment
It is the same account you read, post and publish with — and you will come straight back to this page.

JohneditedPosted Jul 13, 2010, 8:42 AMEdited Jul 13, 2010, 8:43 AM
I have read another article about validation with xml definition. There you need set required object/property class into xml and run Validate when you need. You can find more info on it here .Net validation
mostafa hassanPosted Aug 29, 2009, 3:26 PM
Nice Work
Vishal DograPosted Aug 27, 2009, 6:40 AM
Hi Shiv, Thanks for submitting such a informative article which is short and precise and hence easier to understand. Two limitations, however, occur to me here: 1) Performance: Since validation run on the object and not on the UI elements, think of complex screen which may contain lots of UI elements. In this case we will have to first copy the Ui values to object so that validation can run on it. This may impact the performance. 2) Security: Since the validation rules get copied to .config file in plain text this exposes the business rules and also make them alterable by people with not good intentions. Just want to have your opinion on this and any solutions you mar recommend to overcome them. Vishal