Where is trace.write going?

  • Thread starter Thread starter guy
  • Start date Start date
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.

Have a look at the following links:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/gngrftraceelement.asp
http://msdn.microsoft.com/library/d...en-us/cpgenref/html/gngrflistenerselement.asp

A higher level runtime tracing tool is EIF (Enterprise Instrumentation
Framework):
http://www.microsoft.com/technet/tr...itsolutions/net/maintain/opnetapp/default.asp

Cezary Nolewajka
mailto:[email protected]
remove all "no-sp-am-eh"s to reply
 
Hi,

ASP.NET Page will show trace outputs when you add Trace="True" to page
directive, that is:

<%@ Page Trace="True"...%>

You can also have an application level tracing, more information here:
http://msdn.microsoft.com/library/d...n-us/cpguide/html/cpcontracefunctionality.asp

Try as I may, I cannot get a trace.axd. All aspx @page has trace=true and web.config has trace=true.

My folders look like this

folder1
---default.aspx
---web.config
---folder2
-----default.aspx
-----folder3
----------mydll.dll <=== I need to see trace.write output
 
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.
 
Back
Top