A good 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
"chris" <ne********@boxfrog.com> wrote in message
news:x_********************@comcast.com...
Hello all -
Preface: This isn't a C# Builder question but if you happen to have the
answer to my primary problem, please feel free to chime in ;-)
I'm using Borland's C# Builder (Personal) and it seems there isn't an
Output window (where the Debug.WriteLine() info would go) like VS has. If there
is, I can't find it. I would like to know if it is possible to write a
class with the ability to call a console window that would display the
Debug.WriteLine() info. I am currently working with Windows Forms. I
have read through some documentation but am currently at a loss. Any help
would be greatly appreciated. TIA\
--
chris
