If broken it is, fix it you should

Using the powers of the debugger to solve the problems of the world - and a bag of chips    by Tess Ferrandez, ASP.NET Escalation Engineer (Microsoft)

May, 2006

Posts
  • If broken it is, fix it you should

    .Net exceptions - Tracking down where in the code the exceptions occurred

    • 21 Comments
    I have written earlier about how to track down exceptions using configuration scripts for adplus. Most of the time the methods are short enough that just knowing what function you got an exception in, is enough for you to track down the why, but we all know that we don't live in that perfect world where we write completely modular applications and everything is nicely lined up:) Let's say you have found this exception on the heap... 0:025> !dumpobj 02b7191c Name: System.NullReferenceException...
Page 1 of 1 (1 items)