The client side validation has a number of features: In order to use validators effectively, it helps to have a firm definition of what they are.
Let's refine our previous definition a little: "A validator is a control that checks one input control for a specific type of error condition and displays a description of that problem." This is an important definition, because it means that you frequently need to use more than one validator control for each input control.
Validating text input
In front of each field, we add a Required Field Validator.
If the input field is blank, we want to display an asterisk (*) in front of the field and report a text error in a summary area.
This usually means that if you want to use script to improve the interface of your pages, you have to write the same validation logic twice, once on the client, and again on the server, just in case the client script cannot be executed.
Our objective with validation is as follows: We visited a large number of real pages to determine the sort of scenarios these components needed to be able to handle.
The different types of validators are listed as follows: Write a web page to collect a new user id and password.