You seem knowledgeable here, maybe you can help.

I am using trunk ActiveRecord in an application. I would like to use Rhino.Commons as well, but there is a Nhibernate version conflict as you mentioned. Now looking at what you have here, would this apply to my situation?

I would like to stick to using NHibernate 1.2 as its a stable official release. I would also like to use some things in Rhino.Commons.

Well I believe some of the stuff in RhinoCommon's relies on the NHibernate Trunk (though I could be wrong) ... you could try replacing the NHibernate Lib's in RhinoTools and building it to see what breaks (and then remove those classes) - my work around only addresses the reverse problem (using the NHibernate Trunk + RhinoCommons with the Castle Project, when it's been built targeting NHibernate 1.2).

Generally speaking the easiest way to get up and running with both projects in my experience is.

Checkout CastleProject
Checkout RhinoTools
Replace the Boo Lib's in the CastleProject with those from RhinoTools.
Rebuild the CastleProject
Update the RhinoTools project with the Castle Assemblies you've just built.
Build RhinoCommons
Hack in the version redirection for your project (because the CastleProject was built with NHibernate 1.2)

You can build the CastleProject with the NHibernate Trunk, but that was giving me issues for a while so I reverted back to build with 1.2 and then replacing the assembly with the 2.0 NHibernate lib's in RhinoTools... seems to work just fine.

Ok, thanks. I am no where near the coder Oren Eini is, or you that are most likely. I would not be comfortable running NHibernate trunk anywhere close to a production app. :)

I doubt you would ever strike a problem in the NHibernate Trunk that would cause catastrophic failure for a production site, if the site has passed all the automated tests, and satisfied the test team enough to end up being cut to production then it's hardly going to be a source of problems, especially if you only use builds from the trunk that have passed all the tests (which is what I normally do with the Castle project (though I only care about tests in the core/windsor and monorail... I don't use a lot of peripheral stuff).

Be careful when putting trust into stable builds, in a number of cases the trunk fixes bug's that are in the stable release but weren't identified or resolved in time - that's certainly the case with the Castle Project.