Home > Guides > Programming > .NET and Windows Programming

Toggle Open Guide Table of ContentsGuide Contents

Close Table of ContentsGuide Contents

Close Table of Contents

ASP.NET Trace

Last updated Jan 1, 2004.

Although ASP.NET programs can use the Trace and associated classes to provide runtime program tracing, the ASP.NET runtime environment includes a tracing facility that is specifically designed for Web pages. You can enable this functionality for any Web page with a simple configuration file change, and view diagnostic information about Web requests for that page. In addition, you can write variables or structures to the tracing information, assert that conditions are met, and trace through the page's execution path.

As with the Trace functionality, ASP.NET trace output functions can be left in your production code. They will have no effect on the program's operation unless tracing is enabled in the application's configuration file.

ASP.NET Trace information can be viewed in two ways:

  • If you enable trace output in the application's configuration file, the trace information will be written to the output of the Web page. This feature is very useful during early development and debugging, because you can immediately see the effects of new or changed code.

  • When tracing is enabled in an ASP.NET application, all trace information also is output to the Trace Viewer log. You can use the Trace Viewer application to view the results of a Web request after the fact. Since the trace information is stored on a per-request basis, the Trace Viewer allows you to go back and view previous requests.

Discussions

Copies of the array?
Posted Dec 23, 2008 03:40 PM by luige21
1 Replies
Hi
Posted Dec 5, 2008 05:10 AM by ajay2000bhushan
2 Replies
You have no clue.
Posted Jun 10, 2008 03:28 PM by theinternetmaster
1 Replies

Make a New Comment

You must log in in order to post a comment.

Related Resources

Jim Mischel"Highly unlikely" does not mean "impossible"
By Jim MischelJuly 18, 2009 No Comments

One of my programs crashed the other day in a very unexpected place.  A call to System.Threading.ConcurrentQueue.TryDequeue (from the Parallel Extensions to .NET) resulted in an OverflowException being thrown.  Investigation revealed a pretty serious bug in the System.Random constructor.

It's Here; Put Away Your Pre-Conceptions on What an OS Must Be: Part II
By John TraenkenschuhMay 24, 2009 No Comments

In the last blog in this series, Traenk relates his first experiences with computers and with coding.  But now, some years have passed. . .

It's Here; Put Away Your Pre-Conceptions on What an OS Must Be: Part I
By John TraenkenschuhMay 24, 2009 No Comments

Traenk relates his past experience with Operating Systems that goes back 25 years, ok, more than that but he ain't tellin'

See More Blogs

Informit Network