Some recent ASP.NET fixes (March 2009)


[Updated 8th April 2009. I don’t generally like to change posts after they have been published but I wrote this post while some of the KB articles were still being authored. For a number of reasons there have been some changes to which articles document what issue, so I’m updating the below table to reflect the current situation as accurately as possible]

[Updated 27th April 2009. Correcting some build numbers and adding rollup KB969612]

There have been a few ASP.NET issues lately that have had to be resolved by the production of new hotfixes.

These fixes are recent and are not included in either the Microsoft .NET Framework 3.5 SP1 nor the subsequent .NET Framework Family Update.

When we release a number of fixes at around the same time, it can get a little bit confusing as to which fix package you actually need to get hold of and install in order to resolve the problem you are having. In due course this should be clearly documented in the KB article.

The below tables will hopefully help clarify things a bit. The first column has the link to the KB article that documents the issue. The description column is the high level description of the problem. You then have to decide which operating system you need the fix for. The fix packaging technology is different for different families of operating system. Look in the column appropriate to what you need and look down to the correct row. Either click on the link you find there or, if you see a ‘V’ continue looking down until you find a link or information about how to get the fix.

An important point is the build number. Microsoft hotfixes are always cumulative. So if a fix is included with a particular build of a particular set of files then any later build (higher build number) of the same files will include all previous fixes that affect those files.

Note: at the time of writing this blog post, not all the KB articles describing the problems have been published. So the KB article link may not yet work when you read this. The fixes are available however.

The fix packages in the first table update this set of files:

aspnet_wp.exe
system.web.dll
webengine.dll

I think of these as the “core” ASP.NET files.

The file version number is 2.0.50727.xxxx where xxxx is the build number.

KB describing the problem Description Fix package for Windows 2000/XP/2003 Fix package for Windows Vista SP1 / Windows Server 2008 Build number
KB961847
FIX: Error message when you view a page in design mode after you recompile a .NET Framework 3.5 Service Pack 1-based project: “Error creating control – ‘ControlInstanceName [text]’ could not be set on property ‘PropertyName'”

V

V

4002
KB961864 FIX: Web clients may have several problems when you access an ASP.NET 2.0 AJAX-enabled Web site

V

V

4002
KB961884 FIX: You experience very slow performance on an initial request to an ASP.NET Web site after you change the App_Code folder, the bin folder, or the Global.asax file

V

V

4005

KB962351

FIX: ASP.NET Dynamic menus do not render correctly in IE8 in non-compatibility view

V

V

4007
KB961902 FIX: Error message when you compile an ASP.NET project that contains many application resource files: “A first chance exception of type ‘System.ArgumentException’ occurred in mscorlib.dll”

V

V

4011
KB967535 FIX: A hotfix is available to fix two problems in ASP.NET on IIS 7.0 for Windows Vista and Windows Server 2008 n/a

KB967535

4013
KB969612 Description of the hotfix rollup package for ASP.NET 2.0: April 2009 KB969612   4028

The following fix affects this file:

System.Web.Extensions.dll

KB describing the problem Description Fix package for Windows 2000/XP/2003 Fix package for Windows Vista SP1 / Windows Server 2008 Build number
KB957661 FIX: Exception error message when you use a virtual path provider to serve a Web page that has a ScriptManager control: “Directory ‘<file directory>’ does not exist. Failed to start monitoring file changes.” KB957661 KB957661 4030

HTH

Doug

Skip to main content