Reply to thread

Message

<blockquote data-quote="krntea" data-source="post: 160856" data-attributes="member: 28550">A reference:&quot;SummaryThis article provides a good introduction to the &quot;live debugging&quot; story Microsoft has. There is a robust debugging framework present but, unfortunately, it is not widely known in the developer community. Too often, developers as well as managers take a shot in the dark approach and hope to find a resolution this way. It is easy to take crash and hang dumps in production without having to disturb the production environment. It will take some experience to read these dump files. Nevertheless, it is easy to find out a wealth of information about the application at the time of crash or hang. This article is just an introduction. There are many more commands available. You can find more out about each by using the &quot;!help&quot; command. The following blog by Mike Taulty provides more examples as well as more command descriptions. There are two more articles by John Robbins (article one and article two) that also give a good introduction to this topic. Finally, there is a very comprehensive guide by Microsoft how to debug production .NET applications.&quot;<a href="http://www.codeguru.com/csharp/.net/net_debugging/debugging/article.php/c9595__3/" target="_blank">http://www.codeguru.com/csharp/.net/net_debugging/debugging/article.php/c9595__3/</a></blockquote>

[QUOTE="krntea, post: 160856, member: 28550"] A reference: "Summary This article provides a good introduction to the "live debugging" story Microsoft has. There is a robust debugging framework present but, unfortunately, it is not widely known in the developer community. Too often, developers as well as managers take a shot in the dark approach and hope to find a resolution this way. It is easy to take crash and hang dumps in production without having to disturb the production environment. It will take some experience to read these dump files. Nevertheless, it is easy to find out a wealth of information about the application at the time of crash or hang. This article is just an introduction. There are many more commands available. You can find more out about each by using the "!help" command. The following blog by Mike Taulty provides more examples as well as more command descriptions. There are two more articles by John Robbins (article one and article two) that also give a good introduction to this topic. Finally, there is a very comprehensive guide by Microsoft how to debug production .NET applications." [url]http://www.codeguru.com/csharp/.net/net_debugging/debugging/article.php/c9595__3/[/url] [/QUOTE]

Verification