You can implement a filter in your own assembly and reference it in the configuration file. This should mean that you can make a filter that suites your requirements.
Cheers, Nicko > -----Original Message----- > From: Marco von Frieling [mailto:[EMAIL PROTECTED] > Sent: 17 May 2006 12:35 > To: Log4NET User > Subject: LoggerMatchFilter question > > Hello. > > I would log messages from all types of a specific module (e. > g. caching) to an extra appender, lets say to a > TraceAppender. "Module" means that the classes > functionalities are related to one topic, but they are in > different namespaces and possibly different assemblies. So I > thought I could use the LoggerMatchFilter for this, but it > does not work because the filter uses the > string.StartsWith() method. > But for my szenario it should use the string.Contains() > method. Why is does that filter not exist? Maybe you could > implement it in the same filter with an additional parameter > > <param name="useContains" value="true"/> > > with the default set to false, so that this extension does > not change current behavior? > > Marco > > > -- > Marco von Frieling > In den Ackern 8 > D-27374 Wittorf > > eMail: [EMAIL PROTECTED] > > Echte DSL-Flatrate dauerhaft für 0,- Euro*! > "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl > >
