Quisiera text validating hummmmm
Validating User Input in ASP.NET Web Pages (Razor) Sites
- 10 minutes to read
by Tom FitzMacken
This article discusses how to validate information you get from users — that is, to make sure that users enter valid information in HTML forms in an ASP.NET Web Pages (Razor) site.
What you'll learn:
- How to check that a user's input matches validation criteria that you define.
- How to determine whether all validation tests have passed.
- How to display validation errors (and how to format them).
- How to validate data that doesn't come directly from users.
These are the ASP.NET programming concepts introduced in the article:
- The helper.
- The and methods.
Software versions used in the tutorial
- ASP.NET Web Pages (Razor) 3
This tutorial also works with ASP.NET Web Pages 2.
This article contains the following sections:
Overview of User Input Validation
If you ask users to enter information in a page — for example, into a form — it's important to make sure that the values that they enter are valid. For example, you don't want to process a form that's missing critical information.
When users enter values into an HTML form, the values that they enter are strings. In many cases, the values you need are some other data types, like integers or dates. Therefore, you also have to make sure that the values that users enter can be correctly converted to the appropriate data types.
You might also have certain restrictions on the values. Even if users correctly enter an integer, for example, you might need to make sure that the value falls within a certain range.
Important Validating user input is also important for security. When you restrict the values that users can enter in forms, you reduce the chance that someone can enter a value that can compromise the security of your site.
Validating User Input
In ASP.NET Web Pages 2, you can use the helper to test user input. The basic approach is to do the following:
Determine which input elements (fields) you want to validate.
You typically validate values in elements in a form. However, it's a good practice to validate all input, even input that comes from a constrained element like a list. This helps to make sure that users don't bypass the controls on a page and submit a form.
In the page code, add individual validation checks for each input element by using methods of the helper.
To check for required fields, use (for an individual field) or (for a list of fields). For other types of validation, use . For , you can use these options:
When the page is submitted, check whether validation has passed by checking :
If there are any validation errors, you skip normal page processing. For example, if the purpose of the page is to update a database, you don't do that until all validation errors have been fixed.
- If there are validation errors, display error messages in the page's markup by using or , or both.
The following example shows a page that illustrates these steps.
To see how validation works, run this page and deliberately make mistakes. For example, here's what the page looks like if you forget to enter a course name, if you enter an, and if you enter an invalid date:
By default, user input is validated after users submit the page — that is, the validation is performed in server code. A disadvantage of this approach is that users don't know that they've made an error until after they submit the page. If a form is long or complex, reporting errors only after the page is submitted can be inconvenient to the user.
You can add support to perform validation in client script. In that case, the validation is performed as users work in the browser. For example, suppose you specify that a value should be an integer. If a user enters a non-integer value, the error is reported as soon as the user leaves the entry field. Users get immediate feedback, which is convenient for them. Client-based validation can also reduce the number of times that the user has to submit the form to correct multiple errors.
Even if you use client-side validation, validation is always also performed in server code. Performing validation in server code is a security measure, in case users bypass client-based validation.
Two of the libraries are loadable from a content delivery network (CDN), so you don't necessarily have to have them on your computer or server. However, you must have a local copy of jquery.validate.unobtrusive.js. If you are not already working with a WebMatrix template (like Starter Site ) that includes the library, create a Web Pages site that's based on Starter Site. Then copy the .js file to your current site.
The following page shows how to add client validation features to the example shown earlier.
Not all validation checks run on the client. In particular, data-type validation (integer, date, and so on) don't run on the client. The following checks work on both the client and server:
In this example, the test for a valid date won't work in client code. However, the test will be performed in server code.
Formatting Validation Errors
You can control how validation errors are displayed by defining CSS classes that have the following reserved names:
- . Defines the output of the method when it's displaying an error.
- . Defines the output of the method when there is no error.
- . Defines how elements are rendered when there's an error. (For example, you can use this class to set the background color of an <input> element to a different color if its value is invalid.) This CSS class is used only during client validation (in ASP.NET Web Pages 2).
- . Defines the appearance of elements when there is no error.
- . Defines the output of the method it's displaying a list of errors.
- . Defines the output of the method when there is no error.
The following block shows rules for error conditions.
If you include this style block in the example pages from earlier in the article, the error display will look like the following illustration:
If you're not using client validation in ASP.NET Web Pages 2, the CSS classes for the elements ( and don't have any effect.
Static and Dynamic Error Display
The CSS rules come in pairs, such as and . These pairs let you define rules for both conditions: an error condition and a "normal" (non-error) condition. It's important to understand that the markup for the error display is always rendered, even if there are no errors. For example, if a page has an method in the markup, the page source will contain the following markup even when the page is requested for the first time:
In other words, the method always renders a element and a list, even if the error list is empty. Similarly, the method always renders a element as a placeholder for an individual field error, even if there is no error.
In some situations, displaying an error message can cause the page to reflow and can cause elements on the page to move around. The CSS rules that end in let you define a layout that can help prevent this problem. For example, you can define and to both have the same fixed size. That way, the display area for the field is static and won't change the page flow if an error message is displayed.
Validating Data That Doesn't Come Directly from Users
Sometimes you have to validate information that doesn't come directly from an HTML form. A typical example is a page where a value is passed in a query string, as in the following example:
In this case, you want to make sure that the value that's passed to the page (here, 1022 for the value of ) is valid. You can't directly use the helper to perform this validation. However, you can use other features of the validation system, like the ability to display validation error messages.
Important Always validate values that you get from any source, including form-field values, query-string values, and cookie values. It's easy for people to change these values (perhaps for malicious purposes). So you must check these values in order to protect your application.
The following example shows how you might validate a value that's passed in a query string. The code tests that the value is not empty and that it's an integer.
Notice that the test is performed when the request is not a form submission (). This test would pass the first time that the page is requested, but not when the request is a form submission.
To display this error, you can add the error to the list of validation errors by calling . If the page contains a call to the method, the error is displayed there, just like a user-input validation error.
Working with HTML Forms in ASP.NET Web Pages Sites