Release notes for the ASP.NET Validator package v1.3.2

This releases fixes one bug and adds two features to the feature set of the package.

• Fixed an error that occurred when the culture of the server uses commas as decimal places. An exception was thrown in Validator.IsSupportedBrowser().
• Added the property ClientSideCodeEnabled to the ValidatorEntryClientServer class. This allows individual validators to be disabled on the client side. The Validator property ClientSideCodeEnabled overrides this new property.
• Support for ASP.NET 2.0 beta. This support has some limitations as detailed below.

Limited support for ASP.NET 2.0 beta

Background

Unfortunately with Microsoft's inclusion of validation groups into their validation controls Microsoft has contravened the contract offered by the IValidator interface preventing third party providers of validation controls to seamlessly support validation groups unless the validation controls are implemented exactly as Microsoft has implemented them.

The problem arises when the ValidationGroup property is set on a button control. When the button is clicked, no validation occurs on the server.

Work around

The work around for this issue is more than just a work around, it is actually the recommended way to create validation groups using the Mad! Widgets Validation Package. Very simply, you place the ValidationGroup attribute on a control that is hierarchically higher than the button control. An example of this can be found in Demo 4.

Alternatively, you can use the RegisterGroupForButton method of the Validator object, passing the button control as the first parameter.