Summary
This article describes a hotfix for the ASP.NET browser definition files that are included in the Microsoft .NET Framework 2.0 Service Pack 2 (SP2) and in the Microsoft .NET Framework 3.5 Service Pack 1 (SP1). This hotfix applies to the following operating systems:
-
Windows XP
-
Windows Server 2003
-
Windows Vista
-
Windows Server 2008
-
Windows 7 Service Pack 1 (SP1)
-
Windows Server 2008 R2 Service Pack 1 (SP1)
More Information
This hotfix introduces updated definitions in the browser definition file for Internet Explorer. The browser definition files are stored in one of the following folders, depending on the installed version of the Microsoft .NET Framework:
-
For 32-bit versions of the .NET Framework 2.0 SP2 or of the .NET Framework 3.5 SP1%WinDir%\Microsoft.NET\Framework\v2.0.50727\CONFIG\Browsers
-
For 64-bit versions of the .NET Framework 2.0 SP2 or of the .NET Framework 3.5 SP1%WinDir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\Browsers
By default, ASP.NET uses sniffing technology for the user agent string to detect browsers. The browser definition files cover a certain range of browser versions. However, as the version numbers increase, ASP.NET might not recognize new versions of a browser by using the user agent string. In this case, ASP.NET might handle these versions as an unknown browser. For example, ASP.NET cannot recognize Windows Internet Explorer 10 that has the following user agent string:
Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0)
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must have the Microsoft .NET Framework 2.0 SP2 or the Microsoft .NET Framework 3.5 SP1 installed. Additionally, the computer must be running one of the following operating systems:
-
Windows XP
-
Windows Server 2003
-
Windows Vista
-
Windows Server 2008
-
Windows 7 SP1
-
Windows Server 2008 R2 SP1
Restart information
After you apply this hotfix, you might have to restart the computer if any affected files are being used when you install this hotfix. To avoid a restart of the computer, shut down all web server applications for ASP.NET websites before you apply this hotfix.
Replacement information
This hotfix does not replace a previously-released hotfix.
File information
The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.
For all supported x86-based versions of the .NET Framework 2.0 SP2 or of the .NET Framework 3.5 SP1
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Aspnet_wp.exe |
2.0.50727.5692 |
30,544 |
25-Aug-2011 |
05:07 |
x86 |
|
ie.browser |
Not applicable |
18,411 |
25-Aug-2011 |
05:07 |
Not applicable |
|
System.web.dll |
2.0.50727.5692 |
5,251,072 |
25-Aug-2011 |
05:08 |
x86 |
|
Webengine.dll |
2.0.50727.5692 |
436,048 |
25-Aug-2011 |
05:07 |
x86 |
For all supported x64-based versions of the .NET Framework 2.0 SP2 or of the .NET Framework 3.5 SP1
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Aspnet_wp.exe |
2.0.50727.5692 |
42,320 |
24-Aug-2011 |
23:05 |
x64 |
|
ie.browser |
Not applicable |
18,411 |
24-Aug- 2011 |
21:01 |
Not applicable |
|
System.web.dll |
2.0.50727.5692 |
5,259,264 |
24-Aug- 2011 |
23:10 |
x64 |
|
Webengine.dll |
2.0.50727.5692 |
745,296 |
24-Aug-2011 |
23:05 |
x64 |
Note Because of file dependencies, this hotfix might also contain other files.
Common issue that occurs without this hotfix
Consider the following scenario:
-
You use Windows Internet Explorer 10 to access an ASP.NET-based webpage.
-
The webpage starts a postback.
In this scenario, the postback fails, and you receive the following error message:
Script Error encountered", "'__doPostBack' is undefined
Note The webpage can start a postback in various ways. For example, a LinkButton control can start a postback.
References
The hotfix that applies to the ASP.NET files in the Microsoft .NET Framework 3.5.1 is hotfix 2608565.For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2608565 A hotfix is available for the ASP.NET browser definition files in the .NET Framework 3.5.1Note These ASP.NET browser definition files are part of the Microsoft .NET Framework 3.5.1 that is included in the release to manufacturer (RTM) version of Windows 7 and of Windows Server 2008 R2.For more information about the browser definition file schema, visit the following Microsoft website:
General information about the browser definition file schemaFor more information about the Internet Explorer 10 user agent string, visit the following Microsoft website:
General information about the Internet Explorer 10 user agent stringFor more information about how to detect Internet Explorer more effectively, visit the following Microsoft website:
