I only have experience with the enterprise library for .net 1.1. For
some of the functions to work it requires some services to be running.
It depends on what you are doing but generally I have found it to be
fairly speedy. The problem is that speed is always a relative thing. If
you want to log 1ms intervals then maybe a light weight logger would be
better. For most tasks though I find that it works very well.
Just because it is best practice does not mean it will be fast. The
library is designed to be a very flexable stable and easily
re-configurable. I am sure also speed would have been considered,
however it will always be possible to write an inflexable logger that
was much fast. (In my job a fast logger would probably mean assembler
but that would not be applicable for you.)
You need to work out what you want and then decide on whether to use
it. For a small application that just wants to write details of when it
turned on or off, it would not be appropriate to use it. Just use the
standard .net libraries. For a much larger application the flexability
becomes a real asset and so you would consider using it.
ny***********@gmail.com wrote:
Hi,
Are you using the Microsoft enterpise library? I am considdering using
this in a new project. I am specialy interested in the Logging,
database, and exception modules. Anyone having experience with this? It
seems pretty nice, but I am concerned about the performance. I think
the enterprise library seems pretty heavy, with everything
configurable, but maybe I am completly wrong. It is designed by the
practice and pattern group, so it should be the best practice, right?
