Webinar–Intellitrace for ASP.NET

          If the answer to any of the above questions is YES, then Visual Studio’s “IntelliTrace” is your friend. IntelliTrace literally records the details of an application that can then be played back at any time to debug an issue. This results in faster time to resolution and fewer bug reactivations.  IntelliTrace…

0

!address -summary explained

In order to debug any high memory issue we rely heavily on the output of !address –summary command [You’ll find !address –summary as the part of Ext.dll extension]. We can interpret quite a few things from it which can help us in further debugging. Here’s how For example (for  32 bit app) 0:027> !address –summary…

0

How To View what ASP.NET Requests are doing at runtime on IIS 6.0

This is just a quick blog to mention a forgotten tool.   The managed stack explorer can be run on an IIS 6.0 Server running ASP.NET 2.0 to investigate the managed call stacks.  Looking at the call stacks when an ASP.NET application is not responding may help identify what the requests are doing. Setting up the…

3

IIS 7.0 HTTP Error Pages

Internet Information Services (IIS) 7.0 adds some significant new functionality to the manageability and customization of error messages. The three main areas of improvement when compared to IIS 6.0 are Custom vs. Detailed error pages, better configurability of custom errors, and language-specific custom errors. Custom vs. Detailed error In IIS 7.0, the term “custom error”…

3

Weeking recap of ASP.NET Debugging blog

Here are last weeks updates to the ASP.NET Debugging blog: Code Gallery and CodePlex, how are they different and what are their benefits? An Open Debugger Extension Job openings with the .NET Framework Team ASP.NET Tips- What to gather to troubleshoot – part 1 – High CPU