Sometimes you may want client-side activities to disable a validator. For example, suppose a TextBox is only required if a CheckBox is selected. The TextBox could have a RequiredValidator, but we'd like selecting the CheckBox to enable/disable that validator at the client.
We still need to persist these changes to the server. We can simply enable/disable the validator in the page load:
In summary, ASP.Net provides easy ways to disable a validator based on client activity. This lets us extend the default validator functionality.