Last post Jan 30, 2008 09:53 PM by Sarank
May 29, 2007 06:44 AM|anup_daware|LINK
I am planing to use the Enterprise Library 2.0 Logging Application block, But I am stuck at a very basic design level issue.
Is the loges written to various destinations asynchronously? If it is not asynchronous then its a real disadvantage I see.
Microsoft claims that they have implemented all the best practices internally, but its no where mentioned what exactly they have done to ensure the performance.
If I implement my own Logger I can make it asynchronous and I can score over Application block of enterprise library, moreover I can set the thread priority of the logging thread and get the performance benifit.
Can somebody tell me some strong points supporting the Logging Application Block? And how it overcome the disadvantage of being synchronous (if it is) ?
Enterprise Library 2.0- Logging Application Block
Jun 28, 2007 12:07 AM|anup_daware|LINK
Following is a thread on codeplex: Here I have answered few questions and asked a few more:
And this one comparing Logging Application Block and Log4Net: Defending the Application Block in right manner
Here the MSMQ way for Asynchronous logging with Logging Application Block demonstrated:
Hope this post will help somebody some day :)
Jan 30, 2008 09:53 PM|Sarank|LINK
I came across this posting in Google search. I did not find any solutions in the search other than using MSMQ and distributor service.
So I have put together a simple solution for asynchronous logging using the Enterprise library Logging application block. You can download the sample at
* Saravanan Kanagaraj
Asynchronous logging application block
Asynchronous enterprise library logging application block