Its quite difficult to document every possible usage of a library. In addition 
to these documents:

http://logging.apache.org/log4net/release/config-examples.html
http://logging.apache.org/log4net/release/sdk/log4net.Appender.AdoNetAppender.html
http://logging.apache.org/log4net/release/sdk/log4net.Appender.AdoNetAppenderParameter.Layout.html

There's about 8,000 search results on Google for AdoNetAppender. 

A lot of the documentation is focused on XML examples because that's how the 
majority of the users configure log4net.

I'll glady add your code configuration examples to AdoNetAppenderTest.cs if 
attach them to a JIRA ticket!




________________________________
From: James Green <james.gr...@occam-dm.com>
To: Log4NET User <log4net-user@logging.apache.org>
Sent: Tuesday, June 16, 2009 4:48:27 AM
Subject: RE: Using AdoNetAppender


Hi Again,
 
Surely, this is all pointing to a far bigger problem.  
That is an horrific piece of code!!  Surely this is doable in pure 
C#?
 
I'm amazed that this AdoNetAppender is so poorly 
documented and has so few examples.  It's starting to put me off 
log4net!
 
James.


________________________________
 From: Ron Grabowski 
[mailto:rongrabow...@yahoo.com] 
Sent: 15 June 2009 
22:32
To: Log4NET User
Subject: Re: Using 
AdoNetAppender


This page shows an example of loading an xml string into an XmlDocument 
then configure log4net from the XmlDocument:

http://svn.apache.org/viewvc/logging/log4net/trunk/tests/src/Appender/AdoNetAppenderTest.cs?view=co



________________________________
 From: James Green 
<james.gr...@occam-dm.com>
To: Log4NET User 
<log4net-user@logging.apache.org>
Sent: Monday, June 15, 2009 12:04:16 
PM
Subject: RE: Using 
AdoNetAppender


I think I'm going to have to try the config file method 
first.
 
I'm wrapping log4net and I don't want to cause every 
consuming component to require loads of config information in it just for 
logging purposes.
 
Everything else is a sinch to configure in code, save for 
this appender ... *sigh* ...
 
Cheers,
 
James.
scanned by 
MessageLabs [www.messagelabs.com]

Reply via email to