Overview of how to validate user input (Windows Forms .NET)

When users enter data into your application, you may want to verify that the data is valid before your application uses it. You may require that certain text fields not be zero-length, that a field formatted as a telephone number, or that a string doesn't contain invalid characters. Windows Forms provides several ways for you to validate input in your application.


The Desktop Guide documentation for .NET 7 and .NET 6 is under construction.

MaskedTextBox Control

If you need to require users to enter data in a well-defined format, such as a telephone number or a part number, you can accomplish this quickly and with minimal code by using the MaskedTextBox control. A mask is a string made up of characters from a masking language that specifies which characters can be entered at any given position in the text box. The control displays a set of prompts to the user. If the user types an incorrect entry, for example, the user types a letter when a digit is required, the control will automatically reject the input.

The masking language that is used by MaskedTextBox is flexible. It allows you to specify required characters, optional characters, literal characters, such as hyphens and parentheses, currency characters, and date separators. The control also works well when bound to a data source. The Format event on a data binding can be used to reformat incoming data to comply with the mask, and the Parse event can be used to reformat outgoing data to comply with the specifications of the data field.

Event-driven validation

If you want full programmatic control over validation, or need complex validation checks, you should use the validation events that are built into most Windows Forms controls. Each control that accepts free-form user input has a Validating event that will occur whenever the control requires data validation. In the Validating event-handling method, you can validate user input in several ways. For example, if you have a text box that must contain a postal code, you can do the validation in the following ways:

  • If the postal code must belong to a specific group of zip codes, you can do a string comparison on the input to validate the data entered by the user. For example, if the postal code must be in the set {10001, 10002, 10003}, then you can use a string comparison to validate the data.

  • If the postal code must be in a specific form, you can use regular expressions to validate the data entered by the user. For example, to validate the form ##### or #####-####, you can use the regular expression ^(\d{5})(-\d{4})?$. To validate the form A#A #A#, you can use the regular expression [A-Z]\d[A-Z] \d[A-Z]\d. For more information about regular expressions, see .NET Regular Expressions and Regular Expression Examples.

  • If the postal code must be a valid United States Zip code, you could call a Zip code Web service to validate the data entered by the user.

The Validating event is supplied an object of type CancelEventArgs. If you determine that the control's data isn't valid, cancel the Validating event by setting this object's Cancel property to true. If you don't set the Cancel property, Windows Forms will assume that validation succeeded for that control and raise the Validated event.

For a code example that validates an email address in a TextBox, see the Validating event reference.

Event-driven validation data-bound controls

Validation is useful when you have bound your controls to a data source, such as a database table. By using validation, you can make sure that your control's data satisfies the format required by the data source, and that it doesn't contain any special characters such as quotation marks and back slashes that might be unsafe.

When you use data binding, the data in your control is synchronized with the data source during execution of the Validating event. If you cancel the Validating event, the data won't be synchronized with the data source.


If you have custom validation that takes place after the Validating event, it won't affect the data binding. For example, if you have code in a Validated event that attempts to cancel the data binding, the data binding will still occur. In this case, to perform validation in the Validated event, change the control's Binding.DataSourceUpdateMode property from DataSourceUpdateMode.OnValidation to DataSourceUpdateMode.Never, and add your-control.DataBindings["field-name"].WriteValue() to your validation code.

Implicit and explicit validation

So when does a control's data get validated? This is up to you, the developer. You can use either implicit or explicit validation, depending on the needs of your application.

Implicit validation

The implicit validation approach validates data as the user enters it. Validate the data by reading the keys as they're pressed, or more commonly whenever the user takes the input focus away from the control. This approach is useful when you want to give the user immediate feedback about the data as they're working.

If you want to use implicit validation for a control, you must set that control's AutoValidate property to EnablePreventFocusChange or EnableAllowFocusChange. If you cancel the Validating event, the behavior of the control will be determined by what value you assigned to AutoValidate. If you assigned EnablePreventFocusChange, canceling the event will cause the Validated event not to occur. Input focus will remain on the current control until the user changes the data to a valid format. If you assigned EnableAllowFocusChange, the Validated event won't occur when you cancel the event, but focus will still change to the next control.

Assigning Disable to the AutoValidate property prevents implicit validation altogether. To validate your controls, you'll have to use explicit validation.

Explicit validation

The explicit validation approach validates data at one time. You can validate the data in response to a user action, such as clicking a Save button or a Next link. When the user action occurs, you can trigger explicit validation in one of the following ways:

  • Call Validate to validate the last control to have lost focus.
  • Call ValidateChildren to validate all child controls in a form or container control.
  • Call a custom method to validate the data in the controls manually.

Default implicit validation behavior for controls

Different Windows Forms controls have different defaults for their AutoValidate property. The following table shows the most common controls and their defaults.

Control Default Validation Behavior
ContainerControl Inherit
Form EnableAllowFocusChange
PropertyGrid Property not exposed in Visual Studio
ToolStripContainer Property not exposed in Visual Studio
SplitContainer Inherit
UserControl EnableAllowFocusChange

Closing the form and overriding Validation

When a control maintains focus because the data it contains is invalid, it's impossible to close the parent form in one of the usual ways:

  • By clicking the Close button.
  • By selecting the System > Close menu.
  • By calling the Close method programmatically.

However, in some cases, you might want to let the user close the form regardless of whether the values in the controls are valid. You can override validation and close a form that still contains invalid data by creating a handler for the form's FormClosing event. In the event, set the Cancel property to false. This forces the form to close. For more information and an example, see Form.FormClosing.


If you force the form to close in this manner, any data in the form's controls that has not already been saved is lost. In addition, modal forms don't validate the contents of controls when they're closed. You can still use control validation to lock focus to a control, but you don't have to be concerned about the behavior associated with closing the form.

See also