And this did the trick. I tried to use the PropertyFilter directly, but I
couldn't come up with the property key that represented LoggerName. I tried
loggername, LoggerName, logger, Logger, log4net:logger and log4net:loggername
class NHibernateFilter : StringMatchFilter
{
public override Filte
I'll look into it, thanks.
--- [EMAIL PROTECTED] wrote:
> I would think that you could set up a filter to exclude the NHibernate
> logs. Looking at the code however implies that you might have to write a
> not assembly filter.
>
>
>
>
>
--- Göran Roseen <[EMAIL PROTECTED]> wrote:
> Philip Nelson wrote: "And, I can use injection techniques to add logging
> setup to my apps with minimal coding."
>
> This sounds...eh, interesting! Would you care to elaborate on that?
Sure. As I said I was working with HttpRuntime. More specifica
I would think that you could set up a filter to exclude the NHibernate
logs. Looking at the code however implies that you might have to write a
not assembly filter.
Philip Nelson
Philip Nelson wrote: "And, I can use injection techniques to add logging
setup to my apps with minimal coding."
This sounds...eh, interesting! Would you care to elaborate on that?
/Göran Roseen
Since replies have been light, and my reply to "why not use xml configuration"
might have been a little abrupt, let me elaborate.
I have been a log4net user almost since the first release. I have evangelized
using it for the whole time, just like I evangelized log4j to my java clients
before that.
