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/de...aceelement.asp http://msdn.microsoft.com/library/de...erselement.asp
A higher level runtime tracing tool is EIF (Enterprise Instrumentation
Framework):
http://www.microsoft.com/technet/tre...pp/default.asp
Cezary Nolewajka
mailto:c.*********************@no-sp-am-eh-mail.com
remove all "no-sp-am-eh"s to reply
"guy" <gu*@hotmail.com> wrote in message news:ov********************************@4ax.com...
Where do I get trace output?
Trace.Write("Hello World");