You can create a common layer dll to be referenced by other all dll
files. Then in this common file, there is a public class:
public class Log{
private log=ILog.Logger...//Log4Net interface.
//open the log interface from here
public void DEBUG(string strlog)
{
log.Debug(str
We wrap log4net and have had no issues and we have a logger for each class.
I have not swapped it out as your argument suggests, but I don't like to use
any library directly. It shields you not only from swapping out a library,
but from breaking changes in the library you are wrapping. Most of my
Steve,
If I understand correctly, just have multiple loggers. Perhaps the
"per-class" logger for general diagnostics an trace, and then a more
global "audit" logger you use to write your audit information. You could
use different storage for the two or use the same storage. If you're
using the sam
I second that, but beyond "me-too", the only thing I need that I don't have
currently is aspect-based logging or the equivalent. In general I have
concluded that .net aspect technologies are not-there-yet.
I want to be able to add logging at build or runtime, ideally for runtime I can
just a
I've seen many people wrap log4net just so they could swap it out down the
road..
Doing that, you lose the context sensitivity of having a logger in each
class.. one of log4net's greatest strengths..
And I've never ever seen it actually replaced down the road.. It makes much
more sense to creat
Hello,
I was working on the same problem a few month ago - simply set
appender's threshold to Off. For more details, see archive of this
mailing list and search for subject "Disable/enable appender for all
loggers"
Radovan
From: [EMAIL PROTECTED]
[mailto:
Hello again!
I'm sorry, I messed the words a little, I don't want to
activate/deactivate loggers but the appenders directly (TCP Appender, UDP
Appender and so on)
or better the person I'm doing this for wants to ;-)
bye,
Johannes Frank
Hello!
In a project I'm currently working on, I wish to directly
deactivate/activate certain loggers during runtime so that for example
the server can determine on certain attributes when to log what. I would
realize that by using several loggers, however the person
I'm doing this for wants me
The title says it all really, I would like to be able to route my messages
based on a topic rather than the class that posts the message. For example,
I have an audit requirement and a log requirement for the same class.
When I start/stop a given job, I want to audit that, but I also want to
reco
