Welcome to MSDN Blogs Sign in | Join | Help

Todd's Blog

My contribution to the SharePoint community
ASP.NET 2.0 Fix That Everyone Needs

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 one issue has been the Achilles heal for ASP.NET support and it is documented in 915782.

915782 FIX: You may receive an InvalidCastException error in an ASP.NET-connected Web application

There is one workaround for this issue other than installing the fix and that is to disable batch compilation. Bummer this did not make it into the KB.

To disable batch compilation make the following setting in your web.conf file:

<compilation batch="false"/>

Of course you do not really want to run in production with this setting but if your issue stops after making this change it will confirm you are running into the same issue that we addressed in 915782.

Happy ASP.Netin'

 

Posted: Thursday, May 11, 2006 8:17 AM by Toddca

Comments

Jason Haley said:

# May 11, 2006 10:57 AM

Christopher Steen said:


 A refresh button for asp.net pages [Via: pvanooijen ]
 ASP.NET 2.0 Fix That Everyone Needs [Via:...
# May 23, 2006 10:35 PM

AdamB said:

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 "file not found" c) they don't let you download the hotfix right on the page.

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.
# June 14, 2006 7:11 PM

Toddca said:

AdamB - We have published a KB article and I have blogged about this fix specifically. I am not aware of a "file not found" 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.

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.
# June 15, 2006 11:34 AM
New Comments to this post are disabled
Page view tracker