To promote consistent usage and output by developers, I've created a small library that wraps the .Net Trace class. I would like to persist the results of the trace. The trace will be used from web applications/multiple users. At the conclusion of active tracing, I have a switch that will turn off tracing from either a web.config/app.config file so the overhead of writing the trace will be temporary.I'd really like to keep things simple and direct the results of all of the trace library's results to a single file.
I'd like to avoid using something like database table(s), a queued component or the Event viewer to deal with any persistence concurrency issue. Questions: What is the best and/or least complex method to persist the results of the trace? At a relativly low user volume, will a file persistence be sufficient? I currently write to file from a custom file publisher I created for the MS Exception Management application block. At the low back office usage, I've seen to problems. =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
