Home > Articles > Programming > ASP .NET

Debugging ASP.NET Applications

The days of torturous and painful ASP debugging are over! Discover the new debugging and other diagnostic services provided by ASP.NET and the .NET framework.
This chapter is from the book

Debugging ASP.old applications was generally only slightly less painful than a trip to the dentist. There was a way to debug ASP.old applications, but it was poorly documented and essentially required Visual InterDev and a team of crack technicians, as well as favorable weather conditions and a whole lot of luck to work correctly.

Many ASP.old developers got into the habit of using code like the following as a way of creating breakpoints in their code:

Response.Write "DEBUG: Maybe this will work now."

This is about the least-efficient kind of debugging code you can possibly write. It's the coding equivalent of driving a car off a cliff just to lift up the hood. At the very least, you should have a way of figuring out what's going on in your application without having to stop its execution.

It should come as no surprise, then, that ASP.NET recognized the severe shortcomings in debugging Web applications and came up with a number of compelling solutions. In ASP.NET, you can perform various useful and detailed inspections into the inner workings of your running applications.

Debugging and tracing in ASP.NET applications doesn't require Visual Studio .NET. (This book doesn't assume you have Visual Studio, either.)

We'll begin our exploration of debugging ASP.NET applications with a discussion of tracing and then move on to debugging and other diagnostic services provided by ASP.NET and the .NET framework.

Tracing Your Web Application's Activity

Tracing is a new feature of ASP.NET that enables you to monitor the activity of your application as it runs. Tracing requires three steps:

  1. Equipping a page for tracing

  2. Turning tracing on

  3. Executing your Web application in Trace mode

When you have gone through these three steps, you'll be able to see the results of the execution of each line of code on each page of your ASP.NET application.

Equipping a Page for Tracing

Any ASP.NET pagecan can run in Trace mode. In fact, you technically don't have to explicitly equip a page for tracing to derive benefit from Trace mode. But equipping a page for tracing enables you to insert custom markers in the trace output, so it's common to include them in all but the most trivial ASP.NET pages. Even better, Trace mode can be turned on and off on at the page level or the application level, so you never need to remove the code that equips a page for tracing. Trace code won't affect performance of your application when tracing is turned off, and you'll never have to worry about your embarrassing ad hoc test output making its way to users because you forgot to comment something out.


The Trace object used in ASP.NET is an instance of the TraceContext class, found in the System.Web namespace. (This class is different from the Trace class found in the System.Diagnostics namespace; TraceContext is specific to ASP.NET.)

The properties, methods, and events of the TraceContext class are summarized in the reference section at the end of this chapter.

To equip a page for Trace mode, you make calls to the Write method of the Trace object anyplace in your code you want to receive trace notification. For example, you may be debugging a function that does not appear to be called during the lifetime of the page. By placing a call to Trace.Write somewhere in the body of the function, you can easily determine whether the function is being called.


Because the Trace object is created implicitly by the ASP.NET Page object, you don't need to instantiate it yourself.

Listing 3.1 shows an example of a simple page that is equipped for tracing.

Listing 3.1 A Simple Page Equipped for Tracing with Calls to Trace.Write

<% @Page language="C#" debug="true" trace="true" %>
 <title>ASP.NET DataList Control</title>
<script runat="server">

 public void Page_Load(Object sender, EventArgs e)
  Trace.Write("Page_Load starting.");
  if (!IsPostBack)
   Trace.Write("IsPostBack is false; creating data source.");
   Hashtable h = new Hashtable();
   h.Add ("SF", "San Francisco");
   h.Add ("AZ", "Arizona");
   h.Add ("CO", "Colorado");
   h.Add ("SD", "San Diego");
   h.Add ("LA", "Los Angeles");
   Trace.Write("Data binding.");
   DataList1.DataSource = h;
  Trace.Write("Page_Load ending.");
 <form runat="server">
  <asp:DataList id="DataList1" runat="server" 
   BorderColor="black" BorderWidth="1" CellPadding="3" 
   Font-Name="Verdana" Font-Size="8pt">
   <HeaderStyle BackColor="#000000" ForeColor="#FFFF99"></HeaderStyle>
   <AlternatingItemStyle BackColor="#FFFF99"></AlternatingItemStyle>
    National League West
    <%# DataBinder.Eval(Container.DataItem, "Value") %>
    [<%# DataBinder.Eval(Container.DataItem, "Key") %>]

You may recognize this page as the DataList example from Chapter 2, "Page Framework." (Book authors enjoy recycling their own code as much as any programmers do.) This version of the code includes calls to Trace.Write to indicate the status of the Page_Load event procedure.

You can see the output of this trace simply by navigating to this page in a browser. The normal page code executes and a voluminous amount of trace information is disgorged to the bottom of the page. Under the heading Trace Information, you should be able to see a number of page-generated trace items (such as Begin Init and End Init) as well as the page's own custom trace custom trace messages (such as Page_Load starting).

Categorizing Trace Output

You can assign a category to the trace output generated by your code. Categorizing trace output can make it easier to sort out trace messages; it's particularly useful when you view output in SortByCategory mode (described in the next section).

You assign a category to a trace message by using an overloaded version of the Trace.Write method. Listing 3.2 shows an example of this.

Listing 3.2 Creating Categorized Trace.Write Output

public void Page_Load(Object sender, EventArgs e)
  Trace.Write("My Application", "Page_Load starting.");
  if (!IsPostBack)
   Trace.Write("My Application", "IsPostBack is false;" +
      "creating data source.");
   Hashtable h = new Hashtable();
   h.Add ("SF", "San Francisco");
   h.Add ("AZ", "Arizona");
   h.Add ("CO", "Colorado");
   h.Add ("SD", "San Diego");
   h.Add ("LA", "Los Angeles");

   Trace.Write("Data binding.");
   DataList1.DataSource = h;
  Trace.Write("My Application", "Page_Load ending.");

This is a slightly altered version of the Page_Load event procedure from the previous code example. The only difference is in the pair of strings passed to Trace.Write. When using this form of the method, the first string becomes the category and the second string is the trace message. You can view the trace category alongside the other trace information by viewing the page in Trace mode, as described in the next section.

Enabling Tracing for a Page

You can turn tracing on for a particular page by using an @Page directive. To do this, set the Trace attribute in the @Page directive to true.

<@ Page language='C#' trace="true" %>

Two Trace modes specify how trace output is sorted—by time or by category.

You control the Trace mode by using the TraceMode attribute in the @Page directive. To sort Trace mode information by category, set the TraceMode attribute to SortByCategory. The default setting, SortByTime, sorts the trace output by time, oldest to newest.

When tracing is activated at the page level, a wealth of information is displayed at the bottom of the normal page output. (Depending on what's normally supposed to be displayed on the page, you may have to scroll down to see the trace information.)

Trace information is divided into the following categories:

  • Request details—This includes the session ID assigned to the user's session by ASP.NET, the time the request was made, the encoding used in the request and response, the HTTP type, and the HTTP status code.

  • Trace information—This includes trace information automatically generated by ASP.NET, as well as custom trace items generated by calls to Trace.Write from your code. Included in this information is a measurement of how long each operation took to complete. You can use this information to determine where performance bottlenecks exist in the execution of your page.

  • A control tree—This is a hierarchical display of all the controls on the page.

  • A list of cookies transferred by the request—Unless you have cookie-based sessions turned off in your application, typically at least one cookie will be transferred per request (the cookie used to identify the user's session).

  • HTTP headers—These are sent by the server to the browser.

  • Query string values—Values requested by the browser.

  • HTTP server variables—The list of all HTTP server variables sent by the server to the browser.

Page-based tracing is useful for performance and debugging purposes. But if you're interested in seeing aggregated tracing information—perhaps to determine how multiple users are accessing elements of an entire Web application—you must use application-level tracing, as described in the next section.

Enabling Tracing in an Application

You can turn tracing on for all the pages in a Web application. To do this, you must make a change in Web.config. Listing 3.3 shows an example of a Web.config settings file that activates tracing.

Listing 3.3 Using the Web.config File to Activate Tracing for an Entire Web Directory

   <trace enabled="true" 
     localOnly="true" />

In addition to the enabled and pageOutput settings, you can see that the trace configuration settings in Web.config contain a few options that aren't available in the debug settings found in the @Page directive. Specifically, the requestLimit attribute enables you to limit the number of trace requests stored on the server. This option is meaningful when you view aggregate trace information from a remote browser window, as described in the next section.

The localOnly attribute ensures that trace information can be viewed only by users logged on to the Web server machine directly. This prevents remote users from seeing trace output.

For more information on how Web.config works, see Chapter 5, "Configuration and Deployment."

Using Application Tracing from a Remote Browser Window

When application-level tracing is activated, you can view aggregate trace data from a separate browser window. This gives you an aggregate view of all trace information generated by your Web application.

To do this, first equip the application for tracing by adjusting the appropriate settings in Web.config (as described in the previous section).

Next, open two browser windows: one to view a page equipped for tracing in the application; the second to display trace output. (We'll call this second window the trace window.)

In the trace window, navigate to the HTTP handler trace.axd located in the application directory. For example, if your application is located at http://localhost/myapp/, the Trace mode URL would be http://localhost/myapp/trace.axd. You should be able to see a list of application requests. The list may or may not have any data in it, depending on whether you've refreshed the browser that displays the application page since you started the trace.

After refreshing the application browser a few times, refresh the trace window. You should be able to see a list of trace information. If you navigate to another page in the application and then refresh the trace window, you'll be able to see trace information for that page, too.

You can see that the trace window displays only aggregate information. Further, the number of requests displayed in the window is limited to the number you specified in the Web.config trace setting for the application. You can drill down on each row of information by clicking the View Details link; this displays the same detailed information you see when viewing a single page in Trace mode.


Trace.axd isn't a file; instead, it's a link to an ASP.NET feature known as an HTTP handler. You can use the .NET framework to create your own HTTP handlers; this is discussed in Chapter 8, "HttpHandlers and HttpModules."

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020