You need to run your app with internal logging enabled. This will tell you what configuration is being done internally.
See: http://logging.apache.org/log4net/release/manual/faq.html#internalDebug If the configuration is being reloaded this may cut off your previously attached appender, as this is not specified in the config. The repository will fire events when its config is loaded. E.g. log4net.LogManager.GetLoggerRepository().ConfigurationChanged. You should be able to hook this event to reattach (if required) your appender. Nicko > -----Original Message----- > From: Nathan Dye [mailto:[EMAIL PROTECTED] > Sent: 02 March 2005 17:33 > To: [email protected] > Subject: Memory Appender / Config Merges > > I'm working on a project that uses log4net throughout the > entire application. We're creating a gui for this application > and would like to display logging information within it. > We've created a memory appender and have figured out how to > extract and display event information. > > The problem is that the programmatic configuration of our > memory appender appears to be blown away by the rest of the > application. We're able to get the first part of the logging > information, but eventually our memory appender is cut off > and receives no more logging events. > > What might cause our appender to stop receiving log events > soon after the program initializes our application libraries > and starts executing? > > > Nathan Dye > Systems Engineer > > atlas DMT(tm) > > "Hailed by many online ad professionals as having the best ad > server out there." -Media Magazine > > 206.816.8203 // direct > > 206.816.8909 // fax > > www.atlasdmt.com <http://www.atlasdmt.com/> > > > > Sign up to get the latest digital marketing research at: > > www.atlasdmt.com/contact/signUp.asp > > > >
