Trace Listeners vs. Custom Logging Component
- From: "Jeremy S." <A@xxxxx>
- Date: Wed, 19 Sep 2007 07:42:11 -0700
I'm writing several small utility apps that all need to do some routine
logging of their progress, exceptions encountered, etc. The utilities
include a couple of Console apps, a windows Service, and a couple of Windows
Forms apps.
I was just considering the possibility of implementing the logging
capability via the built-in Trace listeners, rather than writing my own
logging component.
Practically all of the documentation on Trace and Debug classes talks about
using those classes for troubleshooting purposes. But it appears that there
is no reason they can't be used for routine logging purposes.
What would you do and why?... would you prefer to roll your own reusable
logging component or use the Trace and TraceListeners?
Thanks.
.
- Follow-Ups:
- Re: Trace Listeners vs. Custom Logging Component
- From: Arnshea
- Re: Trace Listeners vs. Custom Logging Component
- From: Nicholas Paldino [.NET/C# MVP]
- Re: Trace Listeners vs. Custom Logging Component
- Prev by Date: Re: WaitForExit();
- Next by Date: Re: Trace Listeners vs. Custom Logging Component
- Previous by thread: DllImport not found problem
- Next by thread: Re: Trace Listeners vs. Custom Logging Component
- Index(es):
Relevant Pages
|
