I worked at a financial firm a few years back before the Logging Application Block existed.. Microsoft came to us and asked us what we wanted next from them in the area of Application Blocks.. Logging was one of the choices in their potential near term plans..
Everyone in the room, including those from Microsoft, agreed that log4net was so good that Microsoft should spend it's development time elsewhere. Boy do I wish I had that on video.. A few months later, the Exceptions handling block came out.. Look under the covers, it's the same pattern as log4net.. More months later, and their logging block came out, looking nothing like log4net, or their exception block.. We collectively went WTF, gave up on Microsoft doing anything useful for the Wall Street / Finance community, and moved on.. log4net is still the primary logging mechanism for every dotnet app I've touched in the last 5 years.. Nobody is using Application blocks on a Front office trading platform to the best of my knowledge.. -Peter shaeney wrote: > > Hello all, > > I have been asked to compare the Log4Net library with the Microsoft > patterns > > & practices Logging Application Block. > > > > I have searched this forum but can't find anyone who has asked this > question > > previously. I would have thought this is a common topic. > > > > Does anyone know if this type of side-by-side comparison has been done? > I > > know that both are very extensible, but I am interested in comparing the > > core deliverables. In particular, I am interested in using either for > both > > Logging and Auditing purposes. > > > > Audit will require transactions, which is to say that the calling code > needs > > to know if the Audit message has been persisted or not before it can > > continue. > > > > Cheers, > > Steve > > > >
