I just upgraded to 1.2.9 since I needed the ILoggerRepository.ConfigurationChanged event.
I can't for the life of me figure out what I'm doing wrong with the RemotingAppender. My configuration is very simple, no evaluator on the RemotingAppender, and the Root Level is All. I'm also running a RollingFileAppender (in the same Root logger, again no filters/evaluators) and it's working perfectly. The problem I'm experiencing is this: I have a Windows Service with 3 classes/loggers I should be seeing: company.project.ClassA company.project.Data.ClassB company.project.WindowsService.ClassC In the RollingFileAppender I see all 3 loggers as I should. The RemotingAppender is not though. I verified this by modifying the log4net source and adding a Console.WriteLine(loggingEvent.LoggerName) to the RemotingAppender's SendBuffer() (or whatever the BuffereredAppender.Append() method calls). I'm not seeing the ClassC logger. Mostly. I'll see the first couple calls to it (ClassC is the entry-point), then ClassA and ClassB, but the final ClassC messages are never recieved by the RemotingAppender. Again, it's not as if it's loosing packets or something, it's just never recieving the LoggingEvents at all. This worked fine in Beta8, but I needed the ConfigurationChanged event so I had to upgrade. I'm still using NDC's and assembly:DOMConfigurator, but that's not supposed to be a breaking change in beta9 right?
