Problems with ASP.NET Website with Windows 8.1 / IE 11 Browser

Question

We have an ASP.NET application, we are currently conducting compatibility testing for this in Windows 8.1 / IE 11. We found some problems with the alignment of the user interface, _dopostback and clickbutton. Previously encountered the same problems with Windows 8 / IE 10. These problems are solved by adding the IE browser file to the app_browser folder in the project. But we did not find any last ie.browser file to support IE 11. From some of the blogs it turned out that the fixes were fixed. To solve these problems, by trying and installing hot fixes on the hosted computer, the alignment problems of _dopostback and UI were resolved. The Image button does not work yet.

Answer 1

We cannot upgrade to 4.5 yet. But I was able to create my own ie.browser browser definition file (for 4.0).

In your project, add (or create as) App_Browsers / ie.browser, the following:

<!-- Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv:11.0) like Gecko --> <browser id="IE11Preview" parentID="Mozilla"> <identification> <userAgent match="Trident/(?'layoutVersion'\d+).*rv:(?'revision'(?'major'\d+)(\.(?'minor'\d+)?))" /> <userAgent nonMatch="MSIE" /> </identification> <capabilities> <capability 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" /> <capability name="javascript" value="true" /> <capability name="javascriptversion" value="1.5" /> <capability name="w3cdomversion" value="1.0" /> <capability name="ExchangeOmaSupported" value="true" /> <capability name="activexcontrols" value="true" /> <capability name="backgroundsounds" 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="supportsMaintainScrollPositionOnPostback" value="true" /> <capability name="supportsVCard" value="true" /> <capability name="supportsXmlHttp" value="true" /> <capability name="tables" value="true" /> <capability name="supportsAccessKeyAttribute" value="true" /> <capability name="tagwriter" value="System.Web.UI.HtmlTextWriter" /> <capability name="vbscript" value="true" /> <capability name="revmajor" value="${major}" /> <capability name="revminor" value="${minor}" /> </capabilities> </browser> 

If you are adding to an existing file, look for id = "IE10Plus" - you can change it to id = "IE10", since the Plus part is no longer accurate.

If you can go to 4.5, but if you do not, it can hold you back until you can. Any patches (or updates - for example, to 4.5) will overwrite this - FYI ...

Answer 2

Here's the fix for ASP.NET 4.0:

http://support.microsoft.com/kb/2836939/en-us

Of course, we all crack it ... surprisingly, MSft didn’t even think about testing IE11 against Asp.Net 4.0 before it was released, probably due to the fact that marijuana was recently legalized in Washington State.

Setting up a browser on IE10 also works (provided that the IE10 hotfix for .NET 4.0 is also installed).

Associated change: here is information about user agent changes in ie11. I hope you didn’t rely on driving the material from the user agent string, but I believe that the higher-level / lower-level logic of ASP.NET still uses it in 4.0 and earlier (confirmed by setting UA on IE10 to the server with .net4.0 / ie11 question), but 4.5 supposedly does it differently (see http://www.hanselman.com/blog/IE10AndIE11AndWindows81AndDoPostBack.aspx ).

http://msdn.microsoft.com/en-us/library/ie/bg182625(v=vs.85).aspx

Answer 3

Install .NET 4.5 on the server. It overwrites ASP.NET assemblies with newer versions, where the problem of clicking a button with a known image is resolved.

We also allowed this fix, but the installation of .NET 4.5 was ultimately accepted as our solution.

Answer 4

In my case, the solution was simpler:

• Open IE11 on Windows 8
• Click "Internet Options"
• Click Security
• Go to the Scripting directory (at the end of the list)
• Click the Enable button in the Scripting> Active Scripting section