C sharp validating data
Since only Microsoft Internet Explorer supports VBScript, you'll probably choose Java Script as your primary scripting language to use on a user's computer.
In addition, malicious users can subvert the validation process.
Is there some validation related interface I'm missing? I've worked around the issue for now by creating custom validation attributes and implementing a validation extender component, but I'd still like to know what the accepted best practice is for the scenario posted earlier..
I'm baffled as to why the data binding classes and interfaces sin the CLR fail to address the very common scenario of unchanged null value properties.
Thanks Adam, I've already implemented a similar workaround using custom attributes, but really wanted to know what the official line on best practice is.
It seems strange that MS went so far as to out in the IData Error Info interface, but yet it's so limited in it's usefulness.
What I'm hoping is there's some other interface I've missed, because the way it stands right now the well-known business object interfaces (IEditable Object, INotify Property Changed, IData Error Info) just don't cut it.
Shannon Horn is the co-founder and chief software architect of Web Geniuses Corporation ( Hence, many times validation was not performed in a uniform manner, complex validation was difficult to implement, and Web servers were vulnerable to validation scripts being modified by malicious users.
I currently have a business object base class implementing the following interfaces: IEditable Object, ICloneable, INotify Property Changed, and IData Error Info More specifically, my IData Error Info implementation is like so: [Non Serialized] private Dictionary internal void Set Property Error(string property Name, string error) #endregion This works fine when editing existing (i.e.Users with harmful intent may easily modify the validation script because it is contained in the source of the page that is sent to the user's computer.