I notice that NH is still using 1.2.0 beta 8, but there is a newer version, 1.2.9 beta. It still isn't a "release" version, but there are many new features, and a whole lot of bug fixes. This is also the first release under their Apache partnership (I'm not really sure if that means anything).

I don't think it would involve very many code changes, though it may be a breaking change for some consumers, especially if they've built custom appenders.

Seconded! We use a custom build of NHibernate at work just so we could use 1.2.9 (it's a drop-in replacement if you ignore the DOMConfigurator warnings).

We had to have 1.2.9's ConfigurationReset event for our custom appender, so we can't really do without it. It'd be convenient if we didn't have to use a custom build of NHibernate, the only difference being the log4net version used, but it's a minor nuiscance, so I'm not complaining too loudly. :)

What kind of changes were needed to use the 1.2.9 version? We set the config via DOMConfigurator.Configure(), so I wonder if all would be good if we dropped in the new version and used XmlConfigurator instead.?

It is really annoying to read the log4net docs only to find out after 10 minutes of work that you are working with a 1.2.9 feature/fix which isn't available in NH.

Added NH-286 for log4net.

I use App/Web.config to setup the loggers, so I can't promise anything, but like I said, for us it's a drop-in replacement. DOMConfigurator is still in 1.2.9, it just wraps XmlConfigurator now while it's (DOMConfigurator) being deprecated.

Would you consider attempting this move for 0.9 beta?

Thanks!
-MT

Btw, if this matters to you, you should probably vote on the task (linked above).

-MT

You dont need to use custom build of NHibernate. Because Log4net 1.2.9 is drop-in replacement, NHibernate works with it without any problems. Just need to redirect assembly binder to use different version of log4net assembly. Add following to your application configuration file:


Bye