Yes, it's possible. I created an appender in our a different assembly.
My type value looks somethjing like this:
It's been in production for some time. FYI, we're using version 1.20-b8
-Original Message-
From: Borton, Anthony [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 28, 2004
Hi,
Due to my companies rules, I need to have any component that
communicates to a DB run under COM+. I don't want to have all of Log4Net
running under COM+ so I thought I might just move the ADONETAppender out
to itself own assembly. I tried to do this and update the "type"
attribute in the conf
Hi, I'm trying to get the SQL Server appender working for log4net. I have the
log file appender working, but am having problems with SQL Server.
I traced through the log4net code and in ADONetAppender.cs (line 343 in my
version, 1.2b8), there is this check:
if (m_dbConnection != null && m_dbCon
Hi, I'm trying to get the SQL Server appender working for log4net. I have the
log file appender working, but am having problems with SQL Server.
I traced through the log4net code and in ADONetAppender.cs (line 343 in my
version, 1.2b8), there is this check:
if (m_dbConnection != null && m_dbCon
hi,
i am using log4net in an application project with .net which read from machine.config and when i added these configuration to the machine.config to use the debuger view..it works well
I'm using Chainsaw (build from a few weeks ago) with log4net (even older).
The UDPReceiver started working once I added the UdpAppender to to the
log4net root. In case it helps, here's my log4net configuration: