Debugging and Tracing in ASP.NET AJAX

Sometimes while you're developing an application you need to track potential errors that can creep in post-deployment. Debugging and tracing are two features that come in handy for tracking such errors. In the case of ASP.NET AJAX applications, debugging is a challenge because these applications contain a mix of server-side and client-side code. The client-side code can contain scripts, styles, HTML markups, etc.

However, you can overcome these obstacles and continue to debug and trace your ASP.NET AJAX applications much the same way you debug and trace an ASP.NET application. The Sys.Debug class in the Sys namespace contains a list of methods that you can use to debug your ASP.NET AJAX application, handle trace output, and display the trace messages.

In his WebReference article, Joydip Kanjilal explains these built-in debugging and tracing features and how you can work with them in your ASP.NET Ajax applications.


Read the full story at WebReference:
Debugging and Tracing in ASP.NET Ajax



About the Author

Joydip Kanjilal

Microsoft Most Valuable Professional, Author and Speaker. Featured in "MSDN Featured Developer of the Fortnight (India)" a number of times. Winner of Community Credit Awards at www.community-credit.com several times. Authored numerous books and articles in Microsoft .NET and its related technologies. Authored the following books:-- ASP.NET 4.0 Programming (Mc-Graw Hill Publishing) Entity Framework Tutorial (Packt Publishing) Pro Sync Framework (APRESS) Sams Teach Yourself ASP.NET Ajax in 24 Hours (Sams Publishing) ASP.NET Data Presentation Controls Essentials (Packt Publishing)

Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Download the Information Governance Survey Benchmark Report to gain insights that can help you further establish business value in your Records and Information Management (RIM) program and across your entire organization. Discover how your peers in the industry are dealing with this evolving information lifecycle management environment and uncover key insights such as: 87% of organizations surveyed have a RIM program in place 8% measure compliance 64% cannot get employees to "let go" of information for …

  • With JRebel, developers get to see their code changes immediately, fine-tune their code with incremental changes, debug, explore and deploy their code with ease (both locally and remotely), and ultimately spend more time coding instead of waiting for the dreaded application redeploy to finish. Every time a developer tests a code change it takes minutes to build and deploy the application. JRebel keeps the app server running at all times, so testing is instantaneous and interactive.

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds