views:

2278

answers:

4

Let's say I'm working on a little batch-processing console app in VB.Net. I want to be able to structure the app like this:

Sub WorkerMethod()
   ''//Do some work
   Trace.WriteLine("Work progress")

   ''//Do more work
   Trace.WriteLine("Another progress update")

   ''//...
End Sub


Sub Main()

   ''//Do any setup, like confirm the user wants to continue or whatever

   WorkerMethod()     

End Sub

Note that I'm using Trace rather than Console for my output. This is because the worker method may be called from elsewhere, or even live in a different assembly, and I want to be able to attach different trace listeners to it. So how can I connect the console to the trace?

I can already do it by defining a simple class (shown below) and adding an instance to the Trace's listeners colelction, but I'm wondering if there's a more accepted or built in way to accomplish this:

Public Class ConsoleTrace
    Inherits Diagnostics.TraceListener

    Public Overloads Overrides Sub Write(ByVal message As String)
        Console.Write(message)
    End Sub

    Public Overloads Overrides Sub WriteLine(ByVal message As String)
        Console.WriteLine(message)
    End Sub
End Class
+15  A: 

You can add the following to your exe's .config file.

<?xml version="1.0"?>
<configuration>
    <system.diagnostics>
     <trace autoflush="true">
      <listeners>
       <add name="logListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="cat.log" />
       <add name="consoleListener" type="System.Diagnostics.ConsoleTraceListener"/>
      </listeners>
     </trace>
    </system.diagnostics>
</configuration>

I included the TextWriter as well, in case you're interested in logging to a file.

harpo
upvote for pointing me to System.Diagnostics.ConsoleTraceListner. I'd somehow missed that. I don't otherwise have an app.config, but I can set this up in code easily enough instead.
Joel Coehoorn
That works great for .exe's that have config's, but I have a similar situation but with a DLL. I don't want to modify the calling exe's .config file (it's nunit-console.exe). I'll keep looking, but threw you an up-vote anyway as I certainly learned something.
scottmarlowe
A: 

log4net.

eed3si9n
I also like log4net a lot, but for some situations, or third party code you still might need to redirect the output to console
rslite
+2  A: 

Great solution, but I have a situation where I have different dll's being run by the same calling exe, so I don't want to modify the calling exe's .config file. I want each dll to handle it's own alteration of the trace output.

Easy enough:

Stream outResultsFile = File.Create ("output.txt");
var textListener = new TextWriterTraceListener (outResultsFile);
Trace.Listeners.Add (textListener);

This will, of course, output Trace output to the "output.txt" file.

scottmarlowe
+1  A: 

Joel,

You could do this instead of the app config method:

Trace.Listeners.Add(new ConsoleTraceListener());

or this, if you want to manage adding or removing the listener during the life of the app:

ConsoleTraceListener listener = new ConsoleTraceListener();
Trace.Listeners.Add(listener);

Trace.WriteLine("Howdy");

Trace.Listeners.Remove(listener);

Trace.Close();
Scott P