Debugging, Tracing and Instrumentation in .NET and ASP.NET

Contents

• So, what’s the agenda?
• What is Instrumentation?
• What is debugging and tracing?
• How can we implement debugging and tracing in ASP.NET ?
• How do we view the results of debug and trace?
• So can we see a quick sample of how tracing information can be viewed?
• What if we want to enable tracing in all pages?
• Is it possible to do silent tracing, rather than displaying on the browser?
• How do I persist the instrumented information?
• There is too much noise can we only see information which we need?
• All the above methodologies are for web, how can we do tracing for windows?
• Can we emit different types of trace events like critical, warning, error etc?
• Can we control what kind of information can be routed?
• How can switch off instrumentation?
• It would great if we can summarize?
• References
• Source code

So, what’s the agenda?

Diagnosing a software application is an art and this art has to be more skillful when you go on production.
In development environment you have the complete VS IDE tool so the diagnosing becomes much easier. On production environment as a best practice you do not install visual studio IDE. So on production it’s like fighting with the lion without a knife.

Read more: Codeproject

Posted via email from Jasper-net