Get rid of Paul Glavich's DomValidators and use ASP.NET 2.0 Validation Controls again!? RSS

• • Reply
  

  tobias123

  Member

  365 Points

  122 Posts

  Get rid of Paul Glavich's DomValidators and use ASP.NET 2.0 Validation Controls again!?

  Aug 02, 2007 09:22 AM|LINK

  Hi,

  we have a pretty large web project that was originally written with asp.net 1.1. within it we used Paul Glavich's DomValidators to support client validation in other browsers than only IE.

  Recently we upgraded the project(s) to asp.net 2.0. The asp.net 2.0 Validation controls have improved client validation support so there is no need to still use the DomValidators. Even Paul Glavich posted a comment where he said that.

  Today we have a problem with the DOMValidation.js that the DomValidators include in the HTML to support client validation. We get a client script error on line 126 in IE6: 'event' is null or not an object. Thats the code:

   

  function ValidatorCommonOnSubmit() {
  ///<V1.200> - Support for CausesValidation property
     var retValue = !Page_BlockSubmit;
  
     if (!_val_NS) {   // If we are not in crappy old Netscape 4.7 then....
        if (_val_IE)  // If its Internet Explorer, set our return event value.
           event.returnValue = retValue;
     }
     
     Page_BlockSubmit = false;
  
     return retValue;
  }

  I would like to get rid of the DomValidators and use the ASP.NET 2.0 Validators again. What do i need to do? Do i have to change all controls in my project as the validators are based on own classes?!

  Is there a quick and simple solution to move to the asp.net 2.0 validators?

  Thanks, tob