Matthew, > As always, answers always beget more questions... > > * When I create my logger, do I pass just an arbitrary > value as the logger name?
Yes you can create loggers with any arbitrary name, but there is a hierarchical relationship between loggers. For more information see: http://logging.apache.org/log4net/release/manual/introduction.html#HC-523702 2 > * Is there an equivalent BasicConfigurator attribute as > the DOMConfigurator attribute? There isn't a BasicConfigurator attribute you have to call it programmatically. > * Is it possible for log4net to work with encrypted > configuration files? You mentioned that I could place the > log4net configs into a resource file. Can that file be > secured so developers have no access to it? Log4net cannot work directly with an encrypted configuration file. The DOMConfigurator supports loading the configuration from a Stream. You could load the configuration data, decrypt it, then load it into a MemoryStream object and pass it to the Configure method. > * How can I "black-box" this appender configuration so > other developers can reference an assembly? I want to > abstract the exception database schema from the developers. The only way to do this is to write a separate assembly that exposes a single static Configure() method. This method must then be called during the start-up sequence for your applications. The sooner it is called the better as you cannot log anything until log4net is configured. The Configure method can just call: log4net.Config.BasicConfigurator.Configure(CreateADONetAppender()); The assembly would contain all the code to create the appender. Cheers, Nicko ------------ Nicko Cadell log4net dev
