Category: Debug

First NetExt custom command added by the community – !wsocket

  James Davis is a big shot in the debugging community and maintains a hard core blog of his experiences. Just soon after NetExt came back online he contacted me via the blog with some very particular questions, the kind of question only seasoned debuggers (and debug extension writers) know how to ask. He focused

The case of the non-responsive MVC Web Application

  A colleague (and friend) from Azure team asked me to help narrow down a strange case of a MVC Entity Framework application (hosted in Virtual machine) which occasionally stopped responding, requiring a IIS reset to work again. The products I support do not include IIS, MVC nor Entity Framework. I was invited to help

The strange case of the Application Pool recycling causing high CPU

  This case came as a performance issue. Exchange Web Services stopped responding and CPU skyrocketed. The Exchange team captured a manual dump file and tried in vain to recycle the application. The problem was eventually resolved by invoking a full IISRESET. I was added to the case to help identify why the problem was

Getting started with NetExt

  DISCLAIMER: NetExt is a free and open source WinDBG application that makes .NET debugging much easier as compared to the current options: sos or psscor. This extension is not a Microsoft product and limited support is provided only via its codeplex page. For now I am the only architect/developer, so you may experience delays

Creating DebugDiag rule to generate SharePoint process dump based on ULS Tags

SharePoint has a very comprehensive and configurable diagnostic logging infrastructure known as ULS logs. Most of the ULS log entries include a unique tag called eventId . This tag is a 32-bits field containing only letters and numbers (e.g.. e5mc). This tag can help identify which portion of the code emitted the log. It is