FIX: ValidationSummary (Validator) Controls No Longer Appear After You Upgrade to the .NET Framework 1.1

This article has been archived. It is offered "as is" and will no longer be updated.
Note This articles discusses the ValidationSummary control, however this problem and the hotfix apply to all Validator controls, such as RangeValidator or RequiredFieldValidator.
After you upgrade from the Microsoft .NET Framework 1.0 to the .NET Framework 1.1, the ValidationSummary control may no longer appear in existing ASPX pages that contain that control.

Also, the Page.Validators.Count property has a value of 0, although a ValidationSummary control is on the page.
Note The upgrade process does not cause this problem. This problem occurs in the .NET Framework 1.1.

This problem occurs because Validator controls are not added back to the Page.Validators collection correctly. This behavior might occur when you re-parent (change the parent or the container of) a ValidationSummary control in the control tree. For example, you may experience this problem when you move a ValidationSummary control from the default page collection to a new Forms collection during page Initialization.

This behavior may also occur when you add a UserControl to a page and the UserControl contains a ValidationSummary control.
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft .NET Framework 1.1 service pack that contains this fix.

To resolve this problem immediately, download the fix by clicking the download link later in this article or contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version       Size       File name   -----------------------------------------------------------------------   07-Jul-2003  06:12  1.1.4322.918    253,952  Aspnet_isapi.dll   07-Jul-2003  06:12  1.1.4322.918     20,480  Aspnet_regiis.exe   07-Jul-2003  06:12  1.1.4322.918     32,768  Aspnet_wp.exe   27-May-2003  09:00                   33,522  Installpersistsqlstate.sql   27-May-2003  09:00                   34,150  Installsqlstate.sql   07-Jul-2003  06:12  1.1.4322.918  1,216,512  Sy52106.dll   07-Jul-2003  06:12  1.1.4322.918  1,249,280  System.web.dll   25-Apr-2003  13:32                   14,472  Webuivalidation.js
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

Identyfikator artykułu: 822734 — ostatni przegląd: 02/27/2014 18:44:14 — zmiana: 1.5

Microsoft ASP.NET 1.1, Microsoft Visual Studio .NET 2003 Enterprise Architect, Microsoft Visual Studio .NET 2003 Enterprise Developer, Microsoft Visual Studio .NET 2003 Academic Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbqfe kbbug kbfix KB822734