For that reason, clientside scripting has been used in many cases, but as you probably know, clientside scripting is not bulletproof - it can easily be bypassed or simply turned off. NET, webdevelopers were finally given a good, standard set of tools for validating forms. NET is based on both clientside and serverside technology, which brings the best from both worlds, to make sure that validating a form is as easy as ever. NET 2.0, which is the latest version as I write this, comes with several different validation controls for different purposes.
In the following chapters, we will show examples of each of them.
This kind of situation is handled using validation groups.
To create a validation group, you should put the input controls and the validation controls into the same logical group by setting their Validation Group property.
The client side validation is accomplished through the Client Validation Function property.
The client side validation routine should be written in a scripting language, such as Java Script or VBScript, which the browser can understand.
You can use this validation control to consolidate errors reporting for all the validation errors that occur on a page instead of leaving this up to each and every individual validation control.
The following two mutually inclusive properties list out the error message: Complex pages have different groups of information provided in different panels.
In such situation, a need might arise for performing validation separately for separate group.
Ever since the first dynamic website was created, form validation has been an important subject.
Getting user input through the system requires much attention, and with previous serverside scripting languages, there were no standard way of dealing with form validation.
The validation control classes are inherited from the Base Validator class hence they inherit its properties and methods.