When do I need more than one TraceSource in code?
If one application is writing all its activity data in one log file, is there any use of having more than one TraceSource? I am just curious about the uses cases where one will need more than one TraceSource in the code. wageoghe See these answers to other questions for a good starting point on using TraceSources: can't understand .net 2010 tracing and app.config How to use TraceSource across classes I would say that any time you have more than one class you might (might) consider having more than one TraceSource. One advantage to having more than one TraceSource is that it increases the