James Gregory

It’s here.

For those of you that don’t know, Fluent NHibernate is for helping you map entities with NHibernate. It’s based firmly on the practice of convention-over-configuration, and can be used in a mapping-per-class style using our fluent interface, or let our automapper map your entities itself.

Property getters with side-effects, now there’s a controversial subject if ever I saw one. Don’t do it is the rule; as with any rule though, there’s generally an exception that proves it. If you’re in this situation and you genuinely do have a scenario that requires a property getter to have side-effects, then there’s a side-effect (ha!) that you should be aware of.

It’s nearly here, at long last Fluent NHibernate has nearly reached 1.0. Now starts the official public testing of our 1.0RC.

You can read the release notes on the wiki for more information on what’s changed. There have been a lot of small breaking changes in the fluent interface, mostly reducing it’s verbosity, and a few larger changes elsewhere. Don’t expect to download this and have it just work, because it won’t; hopefully it shouldn’t be too painful though.

Git has been gaining a lot of traction lately, and rightly so. I’ve used it for a couple of years now, for all my projects (Fluent NHibernate and Docu being the prominent ones), but something that hasn’t changed is the tag-line of “but Windows support isn’t very good!”. What you quickly learn is that when people say that, they actually mean there isn’t a Visual Studio plug-in or some similar all-singing all-dancing GUI; this is a dire misrepresentation of Git, because it’s tooling on Windows is excellent if your definition of tooling includes the command-line.

Fluent NHibernate has seen a flurry of development followed by a complete lack of commits, I figure it’s time to let everyone know what’s going on.