Let me guess – you just updated to Internet Explorer 11 and found that the ASP.NET project you are working on fails miserably? You can’t recognize your broken layout, content is all over the place, and you get tons of JavaScript errors?

This post shows you how to update your server to recognize IE11.

The Problem

The problem is quite trivial – a bug in the browser detection under .NET 4. Perhaps you remember how IE10 came out and broke your pages with lots of JavaScript errors? The issue here is the same – these browsers were released after .NET4 and it does not recognize their User-Agent request header.

You can verify that browser detection is causing a problem by using Internet Explorer’s F12 Development tool to temporarily change the User-Agent string sent by the browser. To do so:

  1. Press F12.
  2. Click the Emulation button at the bottom left.
  3. Choose Internet Explorer 9 from the dropdown list.
  4. After the page refreshes, check to see if the page renders correctly.

The Solutions

Of course, you can’t ask your users to do this—but you have three possible solutions to fix your site. I will list them here in the order I suggest you try them. If one does not work, move over to the next:

  1. Install .NET 4.5 on the server – it has the browser detection problem fixed, so you should be all set. We all love simple things – automated installations, cars that drive themselves :)
  2. Yes, I know, .NET 4.5 isn’t available for Windows 2003 Server. Patches are available from Microsoft to update browser detection for older framework versions. (If you tried installing before mid-December 2013, uninstall it and try again.)
  3. If you are still reading, then you may need to update the actual application. Open the App_Browsers folder.
    1. If it has any contents that you do not need – delete them and try again.
    2. If it is empty, the patch failed, and you cannot install .NET 4.5 – add a .browser file that has the correct definitions. I’ve gone and made things easy for you – click this link to download a custom .browser file with the IE11 fix.

That wasn’t so hard, was it?

I hope this was yet another way Telerik helped with your development :)


About the Author

Marin Bratanov

is a Principal Technical Support Engineer in the ASP.NET AJAX division. Ever since he joined Telerik in early 2011 as a novice, his main focus has been improving the services and customer care the company offers. Apart from work, Marin is an avid reader and usually enjoys the worlds of fantasy and Sci-Fi literature. You can find him on Twitter, Goodreads, LinkedIn and GooglePlus.

Related Posts

Comments