Log In
[Expand]Welcome to DevExpress .NET Documentation
[Expand]WinForms Controls
[Collapse]ASP.NET Controls and MVC Extensions
 [Expand]What's Installed
 [Expand]Common Concepts
 [Collapse]ASP.NET WebForms Controls
   Getting Started
  [Expand]Chart Control
  [Expand]Grid View
  [Expand]Card View
  [Expand]Vertical Grid
  [Expand]Rich Text Editor
  [Expand]Image and Data Browsing
  [Expand]Docking and Popups
  [Expand]Site Navigation and Layout
  [Expand]File Management
  [Expand]Multi-Use Site Controls
  [Expand]HTML Editor
  [Expand]Pivot Grid
  [Expand]Tree List
  [Collapse]Data Editors
   [Expand]Product Information
   [Collapse]Common Concepts
     Binding to Data
    [Expand]Mask Editing
      Validation Overview
      Validation Settings
      Validation Error Message
      Validation Summary
       How to: Validate a Particular Editor
       How to: Validate a Group of Editors
       How to: Validate All Editors on a Page
       How to: Implement a Custom Validation
       How to: Determine Editors Validity
    [Expand]List Editors
     Accessibility Support
   [Expand]Editor Types
  [Expand]Spell Checker
  [Expand]Query Builder
 [Expand]ASP.NET MVC Extensions
 [Expand]Redistribution and Deployment
  Get More Help
 [Expand]API Reference
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Document Server
[Expand]Report Server
[Expand]eXpressApp Framework
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation

How to: Implement a Custom Validation

To implement a custom validation, you can handle the server-side ASPxEdit.Validation event or the client-side ASPxClientEdit.Validation event. But it is recommended that you perform both the client-side and server-side validations for security reasons.

Within the events, you can test the editor's edit value, which is accessed via the e.Value/e.value (ValidationEventArgs.Value/ASPxClientEditValidationEventArgs.value) property, against custom validation criteria. If the entered value doesn't meet your restrictions, you can specify the editor as invalid by setting the event parameter's e.IsValid/e.isValid (ASPxEdit.IsValid/ASPxClientEditValidationEventArgs.isValid) property to false. Additionally, you can provide a text explaining why the validation has failed by assigning a descriptive text to the e.ErrorText/e.errorText (ValidationEventArgs.ErrorText/ASPxClientEditValidationEventArgs.errorText) property. When an editor is invalid, the specified text will be displayed within a specific message box.

The code sample below demonstrates how you can perform custom client-side validation to limit an permissible user age. For this purpose, the ASPxClientEdit.Validate event is handled.


An error frame is automatically rendered on the client side in the following situations.

Otherwise the error frame is not rendered to the client side as being unnecessary.

However, in some scenarios you need to perform the editor's validation fully by yourself without using any of the predefined validation capabilities. In these cases, set the ValidationSettings.EnableCustomValidation property to true to force the editor to render the error frame to the client side.

The code sample below demonstrates how you can perform a custom validation without using any predefined validation capabilities. Note that in this case, the ValidationSettings.EnableCustomValidation property should be set to true to show an error frame.

Is this topic helpful?​​​​​​​