<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: ASP.NET Application Looks Like Hell on IE7?</title>
	<link>http://www.netcrucible.com/blog/2007/01/26/aspnet-application-looks-like-hell-on-ie7/</link>
	<description>The software industry from a rational perspective</description>
	<pubDate>Thu, 20 Nov 2008 12:04:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Jack</title>
		<link>http://www.netcrucible.com/blog/2007/01/26/aspnet-application-looks-like-hell-on-ie7/#comment-89241</link>
		<author>Jack</author>
		<pubDate>Tue, 23 Sep 2008 15:42:27 +0000</pubDate>
		<guid>http://www.netcrucible.com/blog/2007/01/26/aspnet-application-looks-like-hell-on-ie7/#comment-89241</guid>
		<description>Just to confirm, this actually works.  I had spent hours trying to find out why my asp.net2 apps did not display the same way in IE6 and IE7.

Until I found this hit, i was at my wits end.

So this does indeed work.  Thanks!</description>
		<content:encoded><![CDATA[<p>Just to confirm, this actually works.  I had spent hours trying to find out why my asp.net2 apps did not display the same way in IE6 and IE7.</p>
<p>Until I found this hit, i was at my wits end.</p>
<p>So this does indeed work.  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scottgu</title>
		<link>http://www.netcrucible.com/blog/2007/01/26/aspnet-application-looks-like-hell-on-ie7/#comment-8870</link>
		<author>scottgu</author>
		<pubDate>Mon, 12 Mar 2007 20:34:22 +0000</pubDate>
		<guid>http://www.netcrucible.com/blog/2007/01/26/aspnet-application-looks-like-hell-on-ie7/#comment-8870</guid>
		<description>Note that to change the DOCTYPE, you just go to the top of the .aspx page and change it like you would with a standard HTML page (it is just standard markup at the top of the page).  So if you are developing a non XHTML compliant page, just change the DOCTYPE or remove it entirely.</description>
		<content:encoded><![CDATA[<p>Note that to change the DOCTYPE, you just go to the top of the .aspx page and change it like you would with a standard HTML page (it is just standard markup at the top of the page).  So if you are developing a non XHTML compliant page, just change the DOCTYPE or remove it entirely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scottgu</title>
		<link>http://www.netcrucible.com/blog/2007/01/26/aspnet-application-looks-like-hell-on-ie7/#comment-8869</link>
		<author>scottgu</author>
		<pubDate>Mon, 12 Mar 2007 20:33:14 +0000</pubDate>
		<guid>http://www.netcrucible.com/blog/2007/01/26/aspnet-application-looks-like-hell-on-ie7/#comment-8869</guid>
		<description>ASP.NET doesn't ever send down a DOCTYPE value - so it isn't ASP.NET sending it down as part of the page.

When you create a new ASP.NET page in Visual Studio, though, it will add a DOCTYPE at the top by default to the blank page.  With VS 2005, this defaults to indicating XHTML Transitional (which is the same output that ASP.NET controls render with).

Assuming you add your own code to the page in an XHTML transitional way, then everything work work fine.  What I ssupect is happening on the pages referenced above is that the developers has added some non-XHTML compliant markup of their own to the page (and not adjusted the DOCTYPE accordingly).  This will then cause issues.

Hope this helps,

Scott</description>
		<content:encoded><![CDATA[<p>ASP.NET doesn&#8217;t ever send down a DOCTYPE value - so it isn&#8217;t ASP.NET sending it down as part of the page.</p>
<p>When you create a new ASP.NET page in Visual Studio, though, it will add a DOCTYPE at the top by default to the blank page.  With VS 2005, this defaults to indicating XHTML Transitional (which is the same output that ASP.NET controls render with).</p>
<p>Assuming you add your own code to the page in an XHTML transitional way, then everything work work fine.  What I ssupect is happening on the pages referenced above is that the developers has added some non-XHTML compliant markup of their own to the page (and not adjusted the DOCTYPE accordingly).  This will then cause issues.</p>
<p>Hope this helps,</p>
<p>Scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: allenjs</title>
		<link>http://www.netcrucible.com/blog/2007/01/26/aspnet-application-looks-like-hell-on-ie7/#comment-7929</link>
		<author>allenjs</author>
		<pubDate>Sat, 27 Jan 2007 03:58:26 +0000</pubDate>
		<guid>http://www.netcrucible.com/blog/2007/01/26/aspnet-application-looks-like-hell-on-ie7/#comment-7929</guid>
		<description>Insane -- Wordpress won't let me paste in a Doctype no matter how I escape it or encode it.  It even strips it if I stick it in CDATA.</description>
		<content:encoded><![CDATA[<p>Insane &#8212; Wordpress won&#8217;t let me paste in a Doctype no matter how I escape it or encode it.  It even strips it if I stick it in CDATA.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Honestas Optima</title>
		<link>http://www.netcrucible.com/blog/2007/01/26/aspnet-application-looks-like-hell-on-ie7/#comment-7917</link>
		<author>Honestas Optima</author>
		<pubDate>Fri, 26 Jan 2007 21:05:52 +0000</pubDate>
		<guid>http://www.netcrucible.com/blog/2007/01/26/aspnet-application-looks-like-hell-on-ie7/#comment-7917</guid>
		<description>There is something missing after this line... "At the top of the .aspx page was the following:"  probably the blog engine filtered out your HTML.

To comment on the post... I am always amazed that a juggernaut like Microsoft does such a good job of keeping all the various programs and components playing together well.  For example, I can take an old Turbo Pascal program that I wrote back in 1992 in MS DOS, and it will still run on Windows XP.  I was also happy to discover that my ActiveX component for Microsoft Word works on Office 97 and all the way up to Office 2007 with 64 bit Vista.

Granted, there are glitches now and again, as you just described.  But, to contrast, I can never install a linux application the same way twice.  Call me bitter, but I just wasted an hour yesterday on an incredibly stupid Cygwin bug, that was carelessly released to the world with a short note in the FAQ.</description>
		<content:encoded><![CDATA[<p>There is something missing after this line&#8230; &#8220;At the top of the .aspx page was the following:&#8221;  probably the blog engine filtered out your HTML.</p>
<p>To comment on the post&#8230; I am always amazed that a juggernaut like Microsoft does such a good job of keeping all the various programs and components playing together well.  For example, I can take an old Turbo Pascal program that I wrote back in 1992 in MS DOS, and it will still run on Windows XP.  I was also happy to discover that my ActiveX component for Microsoft Word works on Office 97 and all the way up to Office 2007 with 64 bit Vista.</p>
<p>Granted, there are glitches now and again, as you just described.  But, to contrast, I can never install a linux application the same way twice.  Call me bitter, but I just wasted an hour yesterday on an incredibly stupid Cygwin bug, that was carelessly released to the world with a short note in the FAQ.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
