Home > Articles > Programming > ASP .NET

  • Print
  • + Share This
This chapter is from the book

This chapter is from the book

Setting Trace Messages

The TraceContext class has a fairly simple interface, with only one constructor, two properties, and two methods. Of course, these are in addition to the standard properties and methods inherited from the Object class. An instance of the TraceContext class is available to your ASP.NET pages through the Trace property of the Page object, so you will need the constructor only if you want to enable tracing in your .NET components (discussed later in this chapter).

TraceContext Properties

The IsEnabled property works the same way as the Trace attribute of the @Page directive. The nice part about having this property available to you is that, unlike the @Page directive, it can be dynamically assigned. For instance, you can specify tracing through a Querystring parameter, as shown in Listings 6.2 and 6.3.

Listing 6.2 Setting the IsEnabled Property Dynamically (C#)

<%@ Page Language="C#" %>
<script language="C#" runat="server">
   protected void Page_Load(object Sender, EventArgs e)
      bool traceFlag = Request.QueryString["trace"] != null
         ? true : false;
      Trace.IsEnabled = traceFlag;

Listing 6.3 Setting the IsEnabled Property Dynamically (Visual Basic .NET)

<%@ Page Language="Visual Basic" %>
<script language="Visual Basic" runat="server">
   Protected Sub Page_Load(Sender As Object, e As EventArgs)
      Dim traceFlag As Boolean = IIF(Request.QueryString("trace")_
         <> Nothing, True, False)
      Trace.IsEnabled = traceFlag
   End Sub

These listings set the IsEnabled property of the Trace object dynamically, based on the presence of the trace Querystring variable. Notice that no Trace attribute is assigned to the @Page directive. It is interesting to note that even if you specify a Trace attribute and set it to false, the IsEnabled property value still dictates whether trace information was displayed to the page.

The real power of using the IsEnabled property is that when you set it to false, the trace information not only isn't displayed, but it also isn't even compiled. This means that you can leave your tracing code in your ASP.NET application when you move it to production. As long as the IsEnabled property is set to false, you will not suffer any performance penalty.

The TraceMode property works exactly like the TraceMode attribute of the @Page directive. The same behaviors and advantages that apply to the IsEnabled property also exist for the TraceMode property.

TraceContext Methods

Only one thing (besides their names) differentiates the two methods of the TraceContext class, Write and Warn: The output generated by the Write method is black, while the output generated by the Warn method is red. For this reason, we will be discussing only the Write method. Just realize that everything said about the Write method can also be applied to the Warn method. There are three overloaded versions of the Write and Warn methods. The first version accepts a trace message. The second version accepts a trace message and a category. The third version accepts a trace message, a category, and an instance of an Exception class. Each of these is covered in more detail next.

TraceContext.Write (string)

The first of the overloaded Write methods of the TraceContext class accepts a single-string parameter. This string contains the message that is displayed in the Message field of the Trace Information section of the trace output (as seen in Figure 6.2). Listings 6.4 and 6.5 demonstrate its use.

Listing 6.4 Implementing TraceContext.Write (string) (C#)

<%@ Page Language="C#" Trace="true" %>
<script language="C#" runat="server">
   protected void Page_Load(object Sender, EventArgs e)
      Trace.Write("I'm tracing now");

Listing 6.5 Implementing TraceContext.Write (string) (Visual Basic .NET)

<%@ Page Language="Visual Basic" Trace="true"
<script language="Visual Basic" runat="server">
   Protected Sub Page_Load(Sender As Object, e As EventArgs)
      Trace.Write("I'm tracing now")
   End Sub

Figure 6.9 shows what the trace output for previous code looks like.

Figure 6.9 Viewing a trace message in the trace output.

Notice the message "I'm tracing now" that appears as the third line item in the Trace Information section. No category was specified, so it is blank. The next overloaded version of the Write/Warn method includes the category parameter.

TraceContext.Write (string, string)

The second overloaded Write method of the TraceContext class takes two string parameters. The first parameter is the category of the trace item. It appears in the Category field of the Trace Information section of the trace output. The second parameter is the message that will be displayed in the Message field, and it is the same as the single-string parameter in the first overloaded Write method.

This is probably the most likely version of the Write method that you will use when debugging your ASP.NET pages. You can assign categories to your trace items, leveraging the TraceMode attribute of the @Page directive or the TraceMode property of the TraceContext class to sort the Trace Information section results. As previously described, this is done using the SortByCategory member of the TraceMode enumeration.

Listings 6.6 and 6.7 demonstrate the use of this version of the Write method.

Listing 6.6 Implementing TraceContext.Write (string, string) (C#)

<%@ Page Language="C#" Trace="true" %>
<script language="C#" runat="server">
   protected void Page_Load(object Sender, EventArgs e)
      Trace.TraceMode = TraceMode.SortByCategory;
      Trace.Write("Category 1", "Category 1 data");
      Trace.Write("Category 2", "Category 2 data");
      Trace.Write("Category 1", "More Category 1

Listing 6.7 Implementing TraceContext.Write (string, string) (Visual Basic .NET)

<%@ Page Language="Visual Basic" Trace="true"
<script language="Visual Basic" runat="server">
   Protected Sub Page_Load(Sender As Object, e As EventArgs)
      Trace.TraceMode = TraceMode.SortByCategory
      Trace.Write("Category 1", "Category 1 data")
      Trace.Write("Category 2", "Category 2 data")
      Trace.Write("Category 1", "More Category 1
   End Sub

Figure 6.10 shows the trace output for the previous code.

Figure 6.10 Viewing a trace message with a category in the trace output.

Notice that the trace items are sorted by category so that both of the category 1 items appear together, instead of being separated by the category 2 item (which was the order in which the code made the calls to the Write method). Also, the previous code uses the TraceMode property of the Trace object to set the sort order. You could alternatively have used the TraceMode attribute of the @Page directive.

TraceContext.Write (string, string, Exception)

The third overloaded version of the Write method takes three parameters. The first two parameters match up with the two parameters of the previous overloaded method call. For the third parameter, you should pass in an object instance of the Exception class or an object instance of a class that inherits from the Exception class. You would most likely use this method call when writing trace output in conjunction with structured exception handling. Listings 6.8 and 6.9 demonstrate this concept by intentionally causing an exception in a Try block that adds to the trace information in the Catch block.

Listing 6.8 Implementing TraceContext.Write (string, string, Exception) (C#)

<%@ Page Language="C#" Trace="true" %>
<script language="C#" runat="server">
   protected void Page_Load(object Sender, EventArgs e)
      int x = 1;
      int y = 0;
         int z = x / y;
      catch(DivideByZeroException ex)
         Trace.Write("Errors","Testing the limits of

Listing 6.9 Implementing TraceContext.Write (string, string, Exception) (Visual Basic .NET)

<%@ Page Language="Visual Basic" Trace="true"
<script language="Visual Basic" runat="server">
   Protected Sub Page_Load(Sender As Object, e As EventArgs)
      Dim x As Integer = 1
      Dim y As Integer = 0
         Dim z As Integer = x / y
      Catch ex As OverflowException
         Trace.Write("Errors","Testing the limits of          
      End Try
   End Sub

Figure 6.11 shows the trace output for the C# version of this code.

Figure 6.11 Viewing a trace message with a category and exception information in the trace output.

In addition to the message that you specify in the call to the Write method, you get the message from the exception that was thrown, as well as the name of the procedure where the exception occurred. You can see valuable debugging information associated with the error that was thrown alongside your own custom comments, making it easier to combine the two into a solution to the bug.

  • + Share This
  • 🔖 Save To Your Account

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