validator - Rumorstore search

ASP.NET has some powerful validation controls that allow us as developers to provide validation in our pages in the context of an object. While they are powerful, they cannot possibly cover all possibilities, so Microsoft has given us the power to design and implement our own validation controls if the built-in validation controls aren't appropriate. These are called Custom Validators and are the focus of this article by David Everhart.<\p>

When you submit an ASP.NET web page, all validation controls on that page are evaluated. But often pages have separate sub-forms, each with submit buttons that should validate only the fields of the form being submitted. For example, a single web page might contain two forms -- a search form and a login form, both containing validators -- which will both be evaluated when either the search button or the login button is clicked. In most cases this behavior is undesired; however, it is a known limitation of the current versions of the ASP.NET Framework (1.0 and 1.1). In this article, Dion Olsthoorn describes a solution to this problem that automatically groups validators, so that only the validators that belong to the same ASP.NET parent control as the clicked button are evaluated. This solution covers both client-side JavaScript and server-side C# code to solve the problem, maintaining client-side validation for Internet Explorer.