;t persist to the next log
> message.
>
> Any thoughts?
>
> Okay, thanks,
> --Chris
>
>
>
> --
> Chris Jerdonek
> Software Developer
> P: (415) 357-3618 Ext. 1357
> Granicus, Inc.
>
>
>
--
View this message in context:
http://www.nabble.com/logging-additional-message-specific-data-with-AdoNetAppender-tp17139552p17185843.html
Sent from the Log4net - Users mailing list archive at Nabble.com.
t;[EMAIL PROTECTED]>
To: Log4NET User
Sent: Saturday, May 10, 2008 10:51:12 AM
Subject: RE: logging additional message-specific data with AdoNetAppender
Thanks for your input, Peter and William.
What I'm leaning towards is making a simple wrapper of LogManager and
ILog so that when I call
tain to.
--Chris
--
Chris Jerdonek
Software Developer
P: (415) 357-3618 Ext. 1357
Granicus, Inc.
-Original Message-
From: William R. Daniels, Jr. [mailto:[EMAIL PROTECTED]
Sent: Friday, May 09, 2008 3:00 PM
To: Log4NET User
Subject: RE: logging additional message-specific data with
Ado
> -Original Message-
> From: Chris Jerdonek [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 08, 2008 7:49 PM
> To: [email protected]
> Subject: logging additional message-specific data with AdoNetAppender
>
> Hi, we've been using log4net for a few
Hi Chris,
You shouldn't need a custom ILog object to do what you want as your second
possibility could be done with MDC/NDC calls.. Yes, you'd have to
pre-populate them before calling log.Info and such.. But that's the only
way I can see of passing along multiple distinct values to the appender
Hi, we've been using log4net for a few months now, and I've been on this list
for about the same. I have a design question.
What would be the "correct" way to do the following?
We'd like to log to a database using the AdoNetAppender. From our code, when
we call things like log.Debug, log.Info
