http://www.iefans.net/windows-server-2003-asp-net-ie11-shibie/
Due to the IE11 of the user-agent string made a large change, so many user-agent to identify the browser program, all corresponding to the occurrence of unrecognized IE11 situation. (This method can be used by the ordinary client.) )
Under the Windows Server 2003 system. NET there is such a problem, with IE11 on the Web site, postback all failed.
A similar problem was previously solved by Chrome under iOS, when site project added a app_browsers directory and then placed a chrome definition.
Results IE11 with the same solution is useless, search for someone said to install Microsoft's hotfix can be resolved, the result loaded several of the same is not effective (because it is Windows Server 2003, so there is no way to install. Net 4.5)
Finally in the foreign site found the corresponding solution, directly to modify. NET directory is finally resolved, the following steps:
Edit the file C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Config\Browsers
Add the following browser definitions:
<!--mozilla/5.0 (Windows NT 6.3; trident/7.0; rv:11.0) like Gecko--><browser id= "Ie11preview" parentid= "Mozilla" > <identification> <userage NT Match= "trident/(? ') Layoutversion ' \d+). *RV: (? ') Revision ' (? ') Major ' \d+) (\. (? ') Minor ' \d+)) " /> <useragent nonmatch= "MSIE"/> </identification> <capabilities> <capab ility name= "Browser" value= "IE"/> <capability name= "layoutengine" value= "Trident"/> <capability name= "layoutengineversion" value= "${layoutversion}"/> <capability name= "IsColor" Value= "true"/> <capability name= "screenbitdepth" value= "8"/> <capability name= "Ecmascriptversion" value= "3.0"/> <capability name= "jscriptversion" value= "6.0"/> <ca Pability name= "JavaScript" value= "true"/> <capability name= "javascriptversion" value= "1.5"/> ; <capability name= "w3cdomversion" value= "1.0"/> <capability name= "exchangeomasupported" value= "t Rue "/> <capability name=" ActiveXControls "value=" true "/> <capability name=" Backgroundsoun DS "value=" true "/> <capability name=" cookies "value=" true "/> <capability name = "Frames" value= "true"/> <capability name= "javaapplets" value= "true"/> < ; Capability Name= "Supportscallback" value= "true"/> <capability name= "Supportsfileupload" value= "true" /> <capability name= "Supportsmultilinetextboxdisplay" value= "true"/> <capability name= "supports MaintainScrollPositionOnPostBack "value=" true "/> <capability name=" Supportsvcard "value=" true "/> <capability name= "Supportsxmlhttp" value= "true"/> <capability name= "Tables" va Lue= "true"/><capability name= "SupportsAccesskeyAttribute" value= "true"/> <capability name= "TagWriter" V Alue= "System.Web.UI.HtmlTextWriter"/> <capability name= "VBScript" value= "true"/> < Capability name= "Revmajor" value= "${major}"/> <capability name= "Revminor" value= "${m Inor} "/> </capabilities></browser>
When you execute c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_regbrowsers.exe-i, restarting IIS resolves an issue that IE11 is not recognized.
If you have any questions about this workaround, you can browse:
http://stackoverflow.com/questions/19783852/
http://stackoverflow.com/questions/18009636/
Windows Server 2003, ASP. NET does not recognize the workaround for IE11 "Go"