[Note: November 2010 Some recent fixes added]
[Note: September 2009 I am in the process of trying to bring this list up to date. It may not be complete]
There is nothing worse than wrestling with a problem for ages only to discover later that there is already a fix for it. I therefore felt it would be useful to summarise what fixes have been done for ASP.NET 2.0 since it was released. Here are a few important points before you go any further:
- What is a hotfix? A good description can be found in this article – Description of the standard terminology that is used to describe Microsoft software updates
- When we ship a fix we always try to minimise the number of files affected. So far, most ASP.NET 2.0 fixes we’ve released only affect three files: System.web.dll, WebEngine.dll and aspnet_wp.exe. The fixes listed in the first table below all update those files to the version number indicated.
- Fixes are cumulative. So for example if you install the fix that says it installs version .832 then you are also getting the bug fix that is described in the article that says it installs version .819, .804 etc., etc. That’s why I’ve written the below table in reverse version number order.
- Check the version number of these files on your system first. If your version number is already higher than the version number indicated in the article then it means you already have that bug fix. If you are getting a problem that sounds like what is described in the article but you already have that fix, then you are probably getting a similar problem or set of symptoms due to some different underlying root cause.
- If for some reason you don’t want that security update but want a more targetted hotfix package for ASP.NET only then the next simplest thing would be to go to the connect site and directly download one of the fix packages for ASP.NET that are available there that includes the fix you are looking for (see below).
- If you are still not sure what fix you need, are having trouble getting hold of a particular fix, are having trouble installing it or have installed it but it hasn’t solved your problem then contact Microsoft Product Support. Scott Guthrie blogged some time ago about a particular hotfix and wrote an excellent introduction to how to contact support (see “Contacting Microsoft Product Support” on that blog entry).
- If you are having a specific problem obtaining or installing a fix or with solving some ASP.NET issue please don’t contact me directly. Unfortunately I cannot scale up to be a one man support organisation. Please utilise Microsoft’s global support organisation as described above.
Fixes that affect the three core ASP.NET 2.0 files of System.Web.dll, WebEngine.dll and aspnet_wp.exe
(located in WindowsMicrosoft.NETFrameworkv2.0.50727)
Fixes that affect System.Web.Mobile.dll
|2.0.50727.803||FIX: You may experience a decrease in the performance of a .NET Framework 2.0-based application when you call the System.Web.UI.MobileControls.Style.GetValue method many times|
Fixes that affect AspNetMMCExt.dll
|2.0.50727.92||FIX: IntelliSense does not work when you use the MMC Snap-In for ASP.NET or the Web Site Administration Tool to add an existing Web.config file to a .NET Framework 2.0 ASP.NET Web site|
Fixes that affect System.Web.Extensions.dll
|3.5.30729.4030||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.”|