I have to admit, I stopped lurking to the Fluent NHibernate mailing list a while ago. Ironically, it wasn't because I thought nothing was going on, simply that the sheer volume of emails was producing massive amounts of noise in my inbox.  The unfortunate aspect of this is that often with .NET projects, there's very little evidence of life outside of their mailing lists (for example, a lot of activity on the Castle project is focusing on Mono and Silverlight, try finding that information on their web site). Now, I know from personal experience just quite how painful it is...

This is definitely in the category of posts "write it down before you stop understanding the solution".  Let's say that you're trying to track your servers.  Servers are related to other servers.  So, for instance, a live server has a corresponding DR server and a corresponding UAT server.  Let's say also you have a simple table with two foreign key references that implements this relationship.  You can implement this in fairly short order:mapping.HasManyToMany(s => s.RelatedSites) .Cascade.All() .WithTableName("RelatedSite") .WithChildKeyColumn("RelatedSiteId") .WithParentKeyColumn("LiveSiteId") .Inverse() .FetchType.Join(); mapping.IgnoreProperty(s =>...

The Castle project has recently got an awful lot better at actually being buildable from SVN.  It used to be a nightmare.  Since Fluent NHibernate doesn't have a recognized built version, you've pretty much got to use the source.  So you'd hope it was pretty easy.  Sadly, it's not.  It's another nightmare.  Most of the problem comes from their decision to use rake. Now, don't get me wrong, I love rake.  It is 100% the right idea for a build tool, but the story on windows sucks.  For one thing, you've got to get ruby working on your machine.  Good...