Matthew, > * How are parameters added to the ADONetAppender > (Exception's stack trace, hostname, other exception or custom > information)? How are "dynamic" parameters passed to the appender?
There are some examples of configuring the ADONetAppender on this page: http://logging.apache.org/log4net/release/config-examples.html Each parameter is a ADONetAppenderParameter object passed to the ADONetAppender's AddParameter() method. The ADONetAppenderParameter specifies the stored procedure or prepared statement parameter name, the database datatype, etc... and a Layout object which is used to render the value of the parameter from the LoggingEvent object. > * How to lock a standard set of appenders for a > development framework? Should a standard config file be used > or a custom component written? How difficult would is it to > implement a component that uses a standard set of appenders > and configurations? If you need to embed a configuration for log4net you can either construct the logging appenders etc.. programmatically or you can embed the configuration file as a resource and then use the DOMConfigurator.Configure(Stream) method to load the configuration with the stream to the embedded resource. > * What is NDC/MDC? What is the significance of NDC and > MDC? And, why should I implement it? The NDC and MDC allow the developer to capture contextual information that is then included in subsequent log messages. For further details see: http://logging.apache.org/log4net/release/manual/contexts.html Cheers, Nicko
