<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>ASP.NET 2.0 Fix That Everyone Needs</title><link>http://blogs.msdn.com/toddca/archive/2006/05/11/asp-net-2-0-fix-that-everyone-needs.aspx</link><description>This entry is much like the one from Aug 2003 where I mentioned important fixes that everyone should install for ASP.Net 1.1. This time however we are talking ASP.NET 2.0. In the last couple of months there has been a rash of problems with CodeDom, specifically</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Interesting Finds</title><link>http://blogs.msdn.com/toddca/archive/2006/05/11/asp-net-2-0-fix-that-everyone-needs.aspx#595403</link><pubDate>Thu, 11 May 2006 17:57:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:595403</guid><dc:creator>Jason Haley</dc:creator><description /></item><item><title>Link Listing - May 23, 2006</title><link>http://blogs.msdn.com/toddca/archive/2006/05/11/asp-net-2-0-fix-that-everyone-needs.aspx#605533</link><pubDate>Wed, 24 May 2006 05:35:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:605533</guid><dc:creator>Christopher Steen</dc:creator><description>&lt;br&gt; &amp;nbsp;A refresh button for asp.net pages [Via: pvanooijen ] &lt;br&gt; &amp;nbsp;ASP.NET 2.0 Fix That Everyone Needs [Via:...</description></item><item><title>re: ASP.NET 2.0 Fix That Everyone Needs</title><link>http://blogs.msdn.com/toddca/archive/2006/05/11/asp-net-2-0-fix-that-everyone-needs.aspx#631547</link><pubDate>Thu, 15 Jun 2006 02:11:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:631547</guid><dc:creator>AdamB</dc:creator><description>This happened to us also on a clean install on a new server. I think it's pretty crummy that a) MS isn't more vocal about it b) they don't update the KB with the correct additional error message &amp;quot;file not found&amp;quot; c) they don't let you download the hotfix right on the page.&lt;br&gt;&lt;br&gt;This is a huge infrastructure problem with ASP.Net 2.0, not some minor glitch. You would think it would have better visibility and at least its own KB article.</description></item><item><title>re: ASP.NET 2.0 Fix That Everyone Needs</title><link>http://blogs.msdn.com/toddca/archive/2006/05/11/asp-net-2-0-fix-that-everyone-needs.aspx#632355</link><pubDate>Thu, 15 Jun 2006 18:34:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:632355</guid><dc:creator>Toddca</dc:creator><description>AdamB - We have published a KB article and I have blogged about this fix specifically. I am not aware of a &amp;quot;file not found&amp;quot; error in relation to this issue however if you could email me offline that information I can have someone investigate and if needed properly call out this error too.&lt;br&gt;&lt;br&gt;Today MSFT does not typically allow for downloading of hotfixes directly however there are talks about changing this policy. The problem here is we need to have some way to track the download of these fixes. Should a regression be found in one of these packages we need to be able to notify those affected of the regression and offer relief. Fixes on Windows Update and the like go through much more rigorous testing. To allow us to deliver hotfixes such as this in a timely manner we increase the risk a bit and ship these fixes sooner rather than later to help those that may really need a fix ASAP.</description></item></channel></rss>