Pages in IE render differently when served through the ASP.NET Development server and Production Server
You see differences in the way IE renders your web application locally on the ASP.NET Development server compared to your production server. Comparing the response from both servers including response headers and CSS show no difference.
The issue may occur because of a setting in IE. In IE, go to Tools –> Compatibility ViewSettings.
The checkbox “Display intranet sites in Compatibility View” turned on forces IE8 to display the web application content in a way similar to how Internet Explorer 7 handles standards mode web pages. Since your local web server is considered to be in the intranet zone, IE uses “Compatibility View” to render your pages.
While you could uncheck this setting in or propagate the change to all developers through group policy settings, a different way is described below.
To force IE to mimic the behavior of a certain version of IE when rendering the pages, you use the meta element to include a “X-UA-Compatible” http-equiv header in your web page or have it sent as part of the header by adding it to your web.config file. The values are listed below:
<meta http-equiv="X-UA-Compatible" content="IE=4"> <!-- IE5 mode -->
<meta http-equiv="X-UA-Compatible" content="IE=7.5"> <!-- IE7 mode -->
<meta http-equiv="X-UA-Compatible" content="IE=100"> <!-- IE8 mode -->
<meta http-equiv="X-UA-Compatible" content="IE=a"> <!-- IE5 mode -->
This value can also be set in web.config like so:
<?xml version="1.0" encoding="utf-8"?>
<add name="X-UA-Compatible" value="IE=EmulateIE7" />
The setting can added in the IIS metabase as described here.
Similarly, you can do the same in Apache by adding the directive in httpd.conf
Header set X-UA-Compatible “IE=EmulateIE7”
Even though it can be done on a site level, I recommend you do it on a per application level to avoid confusing the developer.
Defining Document Compatibility
Implementing the META Switch on IIS
Implementing the META Switch on Apache