Dean, Thank you for your suggestion. It's a good one, and I have thought about it, but since L4N is already doing it (running a separate thread with a FSO) I just wanted to reuse what's already there. If I could just hook in to ConfigureationResetEvent that would be great. Should I be asking this question on log4net-dev also?
Regards, M.G. On 10/25/07, Dean Fiala <[EMAIL PROTECTED]> wrote: > > No need to piggyback on to log4net for this, you can use the > FileSystemWatcher class directly, which is yours free with the .NET > Framework.... > > http://msdn2.microsoft.com/en-us/library/system.io.filesystemwatcher.aspx > > > Regards, > > Dean > > > ------------------------------ > *From:* dawebber [mailto:[EMAIL PROTECTED] > *Sent:* Thursday, October 25, 2007 1:57 PM > *To:* [email protected] > *Subject:* Question about ConfigurationResetEvent > > Hello, all! > > I would like to make use of (and piggyback on) log4net's ability to watch > the app config file for changes. I have a Windows Service, which I would > like to have the ability to reread configuration on the fly, after I edit > the configuration file. > > > > I use the following to init the logger: > > log4net.ILog _logger = log4net.LogManager.GetLogger( > System.Reflection.MethodBase.GetCurrentMethod().DeclaringType); > > > > I can see in the debug output that ConfigurationResetEvent fires when I > change the file. So, that works well. > > > > But, when I try to do this: > > > > _logger.Logger.Repository.ConfigurationResetEvent +=new > log4net.Repository.LoggerRepositoryConfigurationResetEventHandler > (Logger_ConfigurationResetEvent); > > > > My event handler doesn't fire when the config file changes. > > > > Do you guys have any suggestions for me on this? > > > > Thank you in advance. > > > > Regards, > Mark Gimelfarb. >
