ASP.NET & .Net Framework Hotfixes That Everyone Needs
My team works with customers that run into some of the same issues every day. The following fixes should be applied to almost every web server running ASP.NET 1.1.
1. 888419 FIX: You experience out of memory exception errors on a Web server that has ASP.NET 1.1 installed
This fix addresses an issue where we cache a MobileCapabilites infinitely. These objects are about 14,400 bytes each so if you have a few thousand of these can take up quite a bit of memory. This fix is included in the .Net Framework SP1 that ships and is installed with Windows 2003 SP1.
2. 841195 FIX: Slow performance and garbage collection heap memory fragmentation
This fix is very under sold. It is a huge performance win that with huge pay backs if you have slow clients connecting to your website. This fix is included in the .Net Framework SP1 that ships and is installed with Windows 2003 SP1.
3. 900822 FIX: When a Windows Forms-based application uses the System.Threading.Timer class, the timer event may not be signaled in the .NET Framework 1.1 SP1
On the surface this fix would appear to not effect web applications, especially those that do no use Timers. The reality is that all ASP.NET applications use timers internally and that when timer start to not fire all sorts of bad things start to occur. I have seen requests never complete (hung application) and very high memory processes. This fix is post .Net framework 1.1 SP1.
4. 893360 FIX: Generation 1 garbage collections and generation 2 garbage collections occur much more frequently on computers that have 4 GB or more of physical memory in the .NET Framework 1.1
If your web server has more than 2GB of memory you need this fix, period. This fix is post .Net framework 1.1 SP1.
