[update 13/3/12 – added 5719] [update Oct & Nov 2011 – various additions as I find them] [update 23/9/11 added MS11-044 and MS11-028] [update 31/5/11 added .5669] [update 7/4/11 added a load of fixes that I didn’t have listed] [update 29/12/9 added lots of post SP2 hotfixes, MS09-061 versions and added the note on dual-branch servicing] [update 8/10/9 added Windows 7 versions and the post-3.5 SP1 app compat update] [update 5/11/8 added .NET 3.5 SP1, various hotfixes and additional note about "what is the CLR"] [update 20/11/7 added .NET 2.0 SP1] [update 15/11/7 added 4 new recent fixes] Following on from my post about ASP.NET 2.0 fixes, summarised below are the Common Language Runtime (CLR) 2.0 major releases and hotfixes, in version number order. Additional note (5/11/8): the CLR is not synonymous with the .NET Framework as a whole. The CLR is the core runtime engine, including the JIT compiler, metadata management, threadpool, garbage collector etc. The .NET Framework includes the CLR, the base class libraries (BCL), ASP.NET, WCF, WPF and lots more. The below list only relates to CLR fixes.
ASP.NET is a hungry consumer of the CLR services such as threadpool, garbage collection etc. Therefore many of the problems we see customers experience in production ASP.NET applications are the result of issues in the CLR - many of which we have already fixed. So it is always worth considering what patches you currently have installed when something weird happens.
Please read the caveats at the start of the ASP.NET 2.0 fixes post before proceeding.
Following .NET Framework 2.0 SP2, the capability for .NET Framework 2.0 fix packages to carry two different types of fix was introduced. This is referred to as dual branch servicing and is described in this article:
Dual Branch Servicing for the .NET Framework 2.0 Service Pack 2, the .NET Framework 3.0 Service Pack 2, and the .NET Framework 3.5 Service Pack 1
The first occasion I am aware of this capability actually being used is in the MS09-061 release. Therefore it is no longer the case that if the version of mscorwks.dll that you have on your system is higher than the one mentioned in a particular hotfix article that you automatically have the fix described in that article. It depends on what you had on your system prior to installing the dual-branch hotfix package. If you already had a hotfix version of those files installed you would get the LDR version. If you didn’t then you would get the GDR version.
939
943412
You may experience delays when an operating system shuts down if the computer is running a managed service together with the .NET Framework 2.0
930
942708
FIX: You may receive a "SerializationException" exception when you use a class that implements the "INotifyPropertyChanged" interface in an application that is built on the .NET Framework 2.0
926
942084
FIX: Error message if you use the "CspParameters" class to programmatically set a password in an application that is built on the .NET Framework 2.0: "Incorrect PIN"
942027
FIX: You may notice that the memory load is very high when you run an application that is built on the .NET Framework 2.0
That's it for now!
Doug