Chapter 1. Introduction to the Tools
Quite often, I come across developers trying to investigate a particular problem by using either the wrong tools or no tools at all. Strategies range from relying on additional tracing to performing ad-hoc code reviews. By ad-hoc, I mean guessing the general area of the code base where the source of the problem might be. For example, a failure in the transaction service of one system may lead to extensive code reviews of the entire transaction engine even though the problem might lie somewhere else entirely. Sometimes, developers get lucky and the problem is truly located in that piece of code. More often than not, the source and the symptom may be far apart. By utilizing more powerful investigative tools, ...
Get Advanced .NET Debugging now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.