Thanks. I assume that associating an assembly to a repository must be done programmatically as opposed to configuration?
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, April 11, 2005 3:05 PM To: [email protected] Subject: RE: Configuration Usage/Behaviour question > I've got a general question. Am I correct in thinking that > if I've got an application that consists of the exe and > several dozen dynamically used assemblies, I can have each > using its own log4net config file to control the logging > specific to that assembly (basically each assembly/namespace > has its own unique logger in this case)? If I'm not mistaken, this will work provided that each assembly has it's own named logging repository and provides a mechanism for specifying the config file to use. In practice, it's quite common for assemblies to use the default logging logging repository and (in some cases) to assume that logging is configured only via the app/web config.
