Erwyn van der Meer

Thanks for this much needed TraceListener. You can be sure that someone will be testing it and putting it to good use eventually. I will provide you with any feedback as needed.

This is the number one most needed things that I miss in the released Enterprise Library. Very nice code by the way. You did invest quite some time in developing it.

Thanks for sharing it,

Alois Kraus

How funny, I was looking for this on the 14th of February and could find one so I started building my own. Just when i wanted to do a forum post about it I found this link.

I created a workspace for mine: http://www.gotdotnet.com/Workspaces/Workspace.aspx?id=113101bc-f269-4bb4-be05-3a43008f7019

Erwyn,

All i had was a sinle-threaded testing app and to be honest i haven't done much multi-threaded programming.

I hope you don't mind?

The idea is really really great, I'm wondering why patterns&practices group didn't create such trace listener, do they really think, that single trace file scenario is real?!
Anyway Erwyn, I just wanted to point out, that, I have not managed to hook up file formaters to this listener, output always contains full set of data whatever formater is. Am I missing something?

Hi!
Hmm, this really is strange, I've created a new application, then I've created a new configuration file for it, using EntLib configuration tool. In configuration I've defined single RollingFileTrace listener and single Text formater for it with the following template:
Event Type: {severity}
Event ID: {eventid}{dictionary({newline}{key}: {value})}
DateTime: {timestamp}
Event Description: {message}

and all that is happening - I still receive full set of fields in the log file :/ can this be due to:
{dictionary({newline}{key}: {value})}
?

Well, I'll look into the source code, maybe this way I will find the cause of a problem.

@Vladmir, may sound silly but have you selected the right TextFormatter in the RollingFile TraceListener.

Well I have only 2 formaters, both with the same formatting options :)

It seems to be, that when configuring listener using Enterprise Library Configuration tool "Formatter" setting is not saved into .config file, however if You put it there manually everything works perfectly.

Hi! It's me again :) seems, that I've found the way how to make everything work! Well it could be either workaround or a solution (hope Erwyn will clarify :))) ). So:
in RollingFileTraceListenerNode.cs I
1. removed "private string _formatterName;"
2. in constructor removed "this._formatterName = traceListenerData.Formatter;"
3. in "public override TraceListenerData TraceListenerData" replaced "this._formatterName" with "base.Formatter.Name"
now formatter name is always retreived from base, which is FlatFileTraceListenerNode.
......
But You know, I still have a feeling that I've missed something :/

Well You are welcome! I'm glad to contribute to the development of such great extension!!!

Hi Erwyn,

I did extend the sink with some small improvements.
1. Environment Variable expansion for the file name. So you can configure %LOGDIR%\LogFile.txt
2. ProcessID Expansion to support multi process logging
LogFile_$PID$.txt which is also expanded.

3. Call Flush after each write to ensure that all content is written to disk even when a Environment.FailFast() was called to deal with a fatal error inside the CLR.

Just some ideas to make a good sink even better.

Yours,

Alois Kraus

Ever since we first released Enterprise Library, a lot of people have wanted to be able to log information...

I forgot to mention this on my blog, but last Tuesday I released a new version 0.5.2.0 of my RollingFileTraceListener...