Trace class output goes to trace listeners. You can define your own trace listeners or use the already defined in .Net.
The idea is to use the <trace> element of the application .config file.
You can decide during the
runtime of the Debug/Release (depending whether you use Debug/Trace class),
if the output is directed to any "Listener". You can even declare your own
classes as output sinks using the <listeners> element. This allows you to
send for instance the output to remote machine (TCP/IP?), WebService,
Window, etc. At your will.
If your application is writing trace information (as opposed to single page
trace) you can see it by typing you path plus trace.axd. I don't think the
information is actual in a file. It may be in memory somewhere.
It's actually implemented as an http handler which recieves the request from
an axd extension. See rob howards book for a more detailed explanation if
you care.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.