This page is no longer being updated. Please see this page instead.

[last update - 20th November 2007 - added 938276 and .NET 2.0 SP1 entry,]
[previous update - 31st August 2007 - added 939866,]
[previous update - 3rd August 2007 - corrected some of the versions for current beta products]

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 we go any further:

• What is a hotfix? Make sure you can answer this question before you go ahead and start downloading or installing fixes. A good description can be found on the DevDiv Hotifx Public Availability Pilot Program web site.
• 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.
• At the time of writing, the simplest way to get all the latest, current ASP.NET 2.0 fixes is to go to Microsoft Update and let it scan your system and get all recommended critical updates. This will include MS07-040 which updates significant chunks of the Microsoft .NET Framework 2.0, including ASPNET 2.0.
• 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 has already blogged about one of the recent fixes listed below and has 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 our 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 \Windows\Microsoft.NET\Framework\v2.0.50727)

Other fixes outside of the main set of three files:

Hope this helps!

Doug

[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.

The following fix affects this file:

System.Web.Extensions.dll

HTH

Doug