IE10下ASP.NETPageRequestManager、_doPostBack未定义解决方法

Browser version numbers continue to march on. IE9 is here, IE10 is coming, Firefox 5 and 6 are here with 7 and 8 in the wings, Opera&＃39;s on 11, and Chrome is on, I dunno, somewhere between 14 and 50. Regardless, we&＃39;ll all be on version 99 before The Singularity.

There is a bug in the browser definition files that shipped with .NET 2.0 and .NET 4, namely that they contain definitions for a certain range of browser versions. But the versions for some browsers (like IE 10) aren&＃39;t within those ranges any more. Therefore, ASP.NET sees them as unknown browsers and defaults to a down-level definition, which has certain inconveniences, like that it does not support features like Javascript.

If you want to see this for yourself, create a new, blank Web site (e.g. in Visual Studio 2010), add a control that requires Javascript for postback (good example: ), and then run the site using IE9 (where it works) and IE10 (where it won&＃39;t). View the page source and compare the HTML and Javascript sent to each browser.

A similar bug affects Firefox versions 5 and above, where support for using Javascript to reposition the scrollbar in the browser is not detected. This basically breaks the MaintainScrollbackPositionOnPostBack property for Web Forms pages.

These "misdetection" bugs affect Web Forms pages in both ASP.NET 2 and ASP.NET 4. If you are using ASP.NET Web Pages, or if you&＃39;re using ASP.NET MVC or ASP.NET Web Pages and are not using the Browser object to detect Javascript support, you will not be affected.

FIXES

There are two ways to fix this: one is a machine-wide fix, the other is a way to fix individual sites.

MACHINE-WIDE FIXES

We&＃39;re releasing a hotfix that will fix these, which you&＃39;ll be able to get to via some KB articles. These KBs with fixes are live and are the best way to update your system. The fixes solve the browser-detection issue forever for all sites on a machine. These will be rolled up into future versions of the framework and will eventually also be on Windows Update.

• .NET 4 - http://support.microsoft.com/kb/2600088
• .NET 2.0
  • http://support.microsoft.com/kb/2600100 for Win7 SP1/Windows Server 2008 R2 SP1, Windows Vista/Server 2008, Windows XP/Server 2003
  • http://support.microsoft.com/kb/2608565 for Win7/Windows Server 2008 R2 RTM

What the fixes do is update the ie.browser and firefox.browser files in\Windows\Microsoft.NET\Framework\\Config\Browsers with new and future-proofed versions of these browser definitions. Nothing else is affected.

SITE-ONLY FIXES

If you don&＃39;t have access to the whole machine and/or just want to update a single project, use NuGet to install the App_BrowsersUpdate package. Your site structure in Solution Explorer will then look like the image at right. Note that NuGet uses .NET 4, so for systems that have only .NET 2, you&＃39;ll need to get the ZIP file and put the new browser files in App_Browsers manually.

• .NET 4 Browser Update NuGet Package -http://nuget.org/List/Packages/App_BrowsersUpdate
  • install-package App_BrowsersUpdate
• .NET 2.0 Browser Update NuGet Package - http://nuget.org/List/Packages/App_BrowsersUpdate.net20
  • install-package App_BrowsersUpdate.net20
  • Note that NuGet is VS2010 specific so if you don&＃39;t have nuget.exe and .NET 4, you can also copy the .NET 2 updated browser files into ~\App_Browsers manually from this zip file.

Updating the whole machine is the preferred way to fix this.

SUMMARY

• ASP.NET might not recognize the most current versions of some browsers, and will consequently treat them as down-level browsers. (Basically: no Javascript.)
• The fix is to get updated browser-definition files.
• You can install a machine-wide fix or just fix individual projects.
  • Hotfixes are availble with download links.
    • .NET 4 - http://support.microsoft.com/kb/2600088
    • .NET 2.0 - http://support.microsoft.com/kb/2600100
  • The files will also be part of the next batch of .NET 4 fixes, which are anticipated to ship around January 2012 via Windows Update.
  • The next version of the .NET framework will include all the updated files.

If you&＃39;re interested in more detail than you need, I’ve uploaded the updated versions of firefox.browser and ie.browser files that are expected to ship with the next version of ASP.NET. The files and source is up at my BitBucket repo if you are interested in the details.