Wednesday, 16 February 2011

Debugging, Tracing and Instrumentation in .NET and ASP.NET (14 FAQ) by Shivprasad koirala

A nicely explained article about Debugging, Tracing and Instrumentation in .Net.
This article is posted on Code Project by Shivprasad koirala.
He has explained everything in such a nice way with nice images and videos that you will understand all the pin point of Debugging, Tracing and Instrumentation in .Net.
Let me put some contents from his post:
What is Instrumentation?
Debugging application is not just about pressing F 10 or F 11 and watching “add watch windows” using visual studio IDE. Debugging becomes pretty complex on production environments where the project is deployed in a release mode and you need to figure out till what point the code ran and when did it crash. The worst part is you are enjoying your sleep at home and suddenly someone calls up and says, “Hey! the application crashed in production”.If your application is well planned with proper instrumentation you can just say the person to view the event viewer or a log file for further details and you can give the solution on the phone itself.So defining instrumentation in short, it’s the ability of the application to monitor execution path at critical points to do debugging and measure performance.
What is debugging and tracing?
We would like to enable application instrumentation in two situations while you are doing development and while your application is in production. When you monitor application execution and performance in development stage is termed as “Debugging” and when you do in deployed environment it’s termed as ‘Tracing’.

Thanks to Shivprasad koirala for posting such a useful and knowledgeable articles.
Hats off to you!!!