[ https://issues.apache.org/jira/browse/LOG4NET-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Bodewig updated LOG4NET-133: ----------------------------------- Fix Version/s: 1.2 Maintenance Release > Unable to use default config loading > ------------------------------------ > > Key: LOG4NET-133 > URL: https://issues.apache.org/jira/browse/LOG4NET-133 > Project: Log4net > Issue Type: Bug > Components: Core > Affects Versions: 1.2.10 > Reporter: Manuel Riezebosch > Fix For: 1.2 Maintenance Release > > > Default config loading from app.config with the Log4NetConfigSectionHandler > is not possible, because XmlConfiguratior.Configure(ILoggerRepository > repository), where the ConfigurationManager is used, never gets called. > The DefaultRepositorySelector.ConfigureRepository only loads config when the > (Xml)ConfiguratorAttribute is found in the loaded assembly and calls > Configure(assembly, repository) on this attribute. When using the > XmlConfiguratorAttribute, the XmlConfigurator.Configure(targetRepository, > configFile) gets called, which doesn't use the ConfigurationManager but an > XmlDocument instead. > The most annoying thing is that you are required now to use the > XmlConfiguratorAttribute on assembly level, because otherwise the > configuration is ignored. See DefaultRepositorySelector line 657 for more > details. This is a problem when using calling functions in external > assemblies, for instance with unit testing, because the logging from the > tested object is ignored because the configuration fails to load. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira