ASP.Net 1.1 Update

Dino talk about a nice fix to have <TH> instead of <TD> in the header of a Datagrid.

Well done, but this is already in a rollup package announced in June. The difficulty is the fact that you can have the update only by calling the technical support.

Scott Galloway relay this too. "Incidentally, the hotfix package can only be obtained by calling support...why they can't just make the thing downloadable from ASP.NET is beyond me...Rob Howard - any particular reason? "

Can Microsoft understand that this should be downloadable ? Because a lot of developers are working on accessibility.

I have the update myself, not sure I can post it somewhere. Well I would rather prefer a download from MSDN.

Maybe
Sara Ford can help on the matter ?

For reference this is what the package fix:

  • 812686 FIX: When You Call the Response.ClearHeaders Method in a Custom HTTPmodule, Extra Characters Are Appended to the Output
  • 819612 FIX: Slow Performance When the Browser Capabilities Evaluator Is Removed from the Cache
  • 820621 FIX: Cannot Download WinForm Application Configuration Files
  • 820743 FIX: ASP.NET Performance Counters Cannot Count More Than 113 Loaded AppDomains
  • 820747 FIX: Cannot Attach a User-Mode Debugger to the Aspnet_wp.exe Process Through Image File Run Options
  • 821155 Background Batch Compile May Cause a Deadlock When the Thread Pool Has Been Exhausted
  • 821349 FIX: Embedded Null Characters May Bypass Request Script Validation
  • 821438 FIX: Antivirus Programs May Cause Some Web Applications to Restart Unexpectedly
  • 821758 FIX: Server.Transfer Does Not Invoke IsPostBack in .NET Framework 1.1
  • 822148 FIX: ASP.NET Queues Too Many Requests
  • 822162 FIX: ASP.NET Session Variables Can Be Shared Between Applications When Using SQLServer Session Mode
  • 823028 FIX: HttpApplication.OnThreadEnter May Fail Under Memory Pressure
  • 823030 FIX: DataGrid Made Compliant with Section 508 of the Web Accessibility Initiative (WAI) Guidelines
  • 821346 FIX: AspNetHostingPermission Intersect Does Not Handle NULL Target Correctly
  •  

    1 Comment

    • It says somewhere on the support site that the reason they don't just handout these hotfixes is that they were usually built as a result of a customer calling support and having it made special for them. What does this mean you say? It means that the hotfix was built to address a specific problem and it is &quot;hot&quot; so it doesn't go through many of the testing that goes into fixes that distributed with say a service pack. So, Microsoft doesn't want to just let anyone download a patch built for a specific circumstance with the possibility that it could break things (when the customer may have not even needed it).

    Comments have been disabled for this content.