I have written a similar response on another related post:

I party agree with you. The attributes in System.ComponentModel.DataAnnotations can be used used on an class you are in control of. But when you are using a class from a library, or simply use DataTable, then those attributes are useless. 

In that case it would be nice to implement a range of providers, one which can interpret DataAnnotations, one that can be implemented by user and provider information from another source, like metadata from a DataTable. All those providers provide the same object with (validation)information about the data to be displayed/edited/validated.

 

Also, I'm aware that I can use Reflection to add the RadRange Attribute to Properties that have the DataAnnotations.Range attribute, but would be nice if the control would support the standard attributes out of the box.