从 IE6/XP 到 IE8/Win7 的迁移及其对 ASP.NET 应用程序的影响
我工作的公司正在准备IE8中的应用测试。之前我们一直使用IE6。我们的许多 Web 应用程序都是用 .NET 1.0 和 1.1 编写的，最近的应用程序是用 2.x 和 3.x 编写的。我知道 IE8 有一个 IE7 兼容模式，并且说它有一个怪异模式，但我们大多数应用程序都是为 6 编写的，这一点没有具体提及。 7 的兼容性是 6 的兼容性。我不知道这是否一定会延续到 8。在 6 怪癖模式下，可以毫无问题地运行 5.5 站点。微软的任何发行说明都没有更深入的解释，它是否提到怪异模式符合 6 甚至 5.5，只是它的基础（特定的 DOCTYPE 或没有 DOCTYPE）。
如果有人能够阐明为 IE6 设计的网站和应用程序如何在 IE8 中运行，我们将不胜感激。如果其他人也采取了类似的举措，那么过渡的顺利程度如何？
谢谢。
The company I work for is preparing for application testing in IE8. Previously we have been using IE6. Many of our web applications are written in .NET 1.0 and 1.1 with more recent apps written in 2.x and 3.x. I know IE8 has an IE7 compatibility mode and it says it has a quirks mode, but most of our apps were written for 6, which is not specifically mentioned. Compatibility is for 7, which had a compatibility for 6. I do not know if that is necessarily carried over to 8. In 6 quirks mode was to run 5.5 sites without a problem. With no deeper explanation on any of Microsoft's release notes does it mention quirks mode as 6 compliant or even 5.5, just a basis of what it is (specific DOCTYPEs or no DOCTYPEs).
If anyone could shed some light on how sites and apps designed for IE6 should run in IE8 would be greatly appreciated. If anyone else has made a similar move how smooth was the transition?
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我们公司也做了类似的转变。我们从 IE6 全面转向 IE8，我们注意到的唯一问题与样式有关。现在，如果您决定升级 IIS 服务器，则可能会导致某些 ASP 应用程序无法正常工作。
We made a similar switch in our company. We went from IE6 to IE8 across board, the only issues we noticed were related to styling. Now if you decide to upgrade your IIS server than that might cause some of your ASP apps to not work correctly.
您应该注意的唯一一件事是您已确保 CSS 在 IE8 中正常工作。你可以在 XP 中安装 IE8，看看会发生什么。
ASP.NET 代码并不重要，只需在 HTML、CSS 和 JavaScript 上添加注释即可。
The only thing you should notice is that you have ensured that your CSS will work correctly in IE8. You can install IE8 in your XP and see what will happen.
ASP.NET code is not important, Pay yout attation on HTML,CSS and JavaScript.
Quirks 模式原则上没有改变。 IE8+将其描述为“IE5文档模式”。如果您的页面仍然使用 Quirks 模式，那么：
自 5.5 以来，IE 的每个版本的 bugwards 兼容性都在拖延，除了 IE6。 MS从IE7中放弃了IE6标准模式兼容性，然后发现随之而来的兼容性问题使得很难推动人们升级到IE7（从而抑制了Vista的企业销售）。从那时起，他们就确保每个 IE 版本都有模拟其前身的模式，但为时已晚，无法恢复 IE6 标准模式支持。
如果某个白痴没有将浏览器与操作系统“集成”，那么这种灾难性的混乱就不会发生。如果不是这样，我们都可以只运行我们需要的应用程序所需的独立 IE 版本。
文档渲染模式只是故事的一半。让 JavaScript 一致地工作通常是一个更大的问题，特别是如果代码一开始就是肮脏的、不可靠的 hack（对于针对 IE6 的 Web 应用程序来说，通常就是这样）。另一方面，已经在 Firefox 和其他更符合标准的浏览器上运行的 Web 应用程序应该可以在 IE8 上运行，几乎不需要任何更改。
Quirks Mode has in principle not changed. IE8+ describes it as “IE5 document mode”. If your pages are still using Quirks Mode, then:
IE is dragging along bugwards-compatibility for every version of IE since 5.5 except IE6. MS dropped IE6-standards-mode compatibility from IE7, then found the ensuing compatibility problems made it difficult to push people to upgrade to IE7 (and consequently depressed corporate sales of Vista). Since then they've made sure that each IE release has modes to simulate its predecessors, but it was too late to bring back IE6-standards-mode support.
This disastrous mess would never have happened if some idiot hadn't “integrated” the browser with the OS. If it weren't for that we could all just run the standalone IE versions we needed for the apps we needed.
And document rendering mode is only half the story. Getting the JavaScript to work consistently is often more of a problem, especially if the code was a dirty unreliable hack in the first place (which, in the case of webapps aimed at IE6, it often is). On the other hand, webapps that already worked on Firefox and other more standards-compliant browsers should work on IE8 with little to no change.