This is my personal blog. The views expressed on these pages are mine alone and not those of my employer.

Tuesday, 19 January 2010

Validatation for Custom User Controls

Recently I stumbled across the problem of needing to validate user input supplied to a Custom User Control.  Usually validation is simply the case of dragging one of the excellent validation controls onto the page and pointing it towards the control you wish to validate.

Custom User Control's however are a different story.  These are controls written by a developer to carry out a function which no other existing controls can.  As they have been written from the ground up, they cannot be simply associated to a validation control without further work.

To allow a Custom User Control to be validated the first thing which is required is the addition of <ValidationPropertyAttribute("value")>.  This specifies the property which supplies the string to be validated, where "value" is the name of the property.

Secondly the ControlToValidate="" property of validation control on the page should be the ID of the user control, colon(:), then the ID of the control to which 'value' is associated.

For example I had a control named cboTask which had <ValidationPropertyAttribute("value")> defined within it where value was a property which returned the current value of a DropDownList (DropDownList1) which was contained within cboTask.  In order to validate that the user selected an option I used the RequiredFieldValidator with the ControlToValidate="cboTask:DropDownList1".

   1:  <ValidationPropertyAttribute("value")> _
   2:  Partial Public Class ctlDropDownList
   3:      Inherits System.Web.UI.UserControl
   6:   Public Property value() As String
   7:          Get
   8:              Return DropDownList1.SelectedValue.Trim()
   9:          End Get
  10:          Set(ByVal value As String)
  11:              Dim llistitem As ListItem
  12:              DropDownList1.ClearSelection()
  13:              For Each llistitem In DropDownList1.Items
  14:                  If RTrim(llistitem.Value) = RTrim(value) Then
  15:                      llistitem.Selected = True
  16:                      Exit For
  17:                  End If
  18:              Next
  19:          End Set
  20:      End Property
  22:  End Class

   1:  <asp:RequiredFieldValidator ID="rfvTask"
   2:         runat="server"
   3:         ErrorMessage="Task cannot be blank"
   4:         InitialValue=""
   5:         ControlToValidate="cboTask:DropDownList1"
   6:          ValidationGroup="page">*</asp:RequiredFieldValidator>

Doing this allows both client and server validation, and allows you to use the validation controls as you would with any of the existing .NET controls.


  1. Simple and efficient

  2. It took me Days of debugging trying to get this to work before finding this artical... It was the control:subcontrolID that was the key for me. Thank you so much for this!!

  3. This got me in the right direction, thanks! One point I came across through...

    I used the form controlID:subcontrolID without adding the ValidationPropertyAttribute attribute to my user control class and everything still worked fine. I am only doing server side validation, perhaps that makes a difference.

  4. I really like examining and also following ones write-up when i locate them incredibly beneficial and also fascinating.
    That write-up is usually just as beneficial along with fascinating.Verification and Validation both are independent type of testing. Obviously,
    If we look both of these activities as a whole, we can also call it testing.


    1. Verification and Validation are the activities performed to improve the quality and reliability of the system and assure the product satisfies the customer needs.
      Verification assures the product of each development phase meets their respective requirements.
      Validation assures the final product meets the client requirements.

      software validation

  5. This applies not only during the IQ, OQ and PQ validation phases, but far earlier,
    beginning with the first meeting, and continuing through analysis of your process.
    Software validation is a part of the design validation for a finished device,
    but is not separately defined in the Quality System regulation.

    software validation

  6. Thank you for sharing