Hi Ian,
That does seem quite complicated, and beyond what Ive done with log4net. The
only mod I needed was my extra appender class. You might have luck trying to
extend the LoggingEvent class, it may allow you to keep the config nice and
dynamic as in your example. Or maybe you could extend A
Thanks for that - I was thinking along the lines of pass my XML in as the
message. The only problem with that was the fact that it didn't seem to fit
in with the config 'philosophy' of log4net. I'd had hoped that I could
somehow create my own LoggingEvent to pass in, and then change my app.config
t
Ron--
I can address your question indirectly and anecdotally.
FWIW, we looked at logging to the file system on our web server.
The security implications of giving an application rights to write to disk
was major concern of our web server administration team.
Another important consideration was
will all work (the first one logs into a subdir of the current
directory named Data/Logs, the second into a sibling dir, the third
into a directory off the current drive's root).
I don't know of any way to put the current user's home directory in
there; you could try %USERPROFILE%/Data/Logs/log
Thanks for the explination. I have another question now. When using the
ThreadContext.Stacks, what pattern conversion character do you use to read
it? Is it stored in the properties collection? For example ...
using(ThreadContext.Stacks["OrderID"].Push(orderId))
{
// The above message will b
I´m having problems with the RollingFileAppender when i´ve deployed my
application to the live server, i can´t get it to work.
This is my web.config
Paul,
The ThreadContext stores data in a thread local slot. This is attached
to a specific runtime thread. In v1.0 and v1.1 this thread corresponds
to an OS thread. The ThreadContext data is limited to that one thread
and not visible from other threads.
The LogicalThreadContext stores its data in
On my dev machine, I have several appenders that write to various log
files:
When I move this to a different server, the file path won't always be
C:\inetpub\wwwroot\testsite... Is there a way I can use a relative path
on the param tag or on the log4net tag?
Its a pain having to make sure a
