Question

I’m taking a complicated legacy schema and mapping it with Fluent NHibernate. The schema is wacky enough that I’ve given up on automapping; the relationships between tables are weird and complicated, and it would involve a ton of exceptions.

The thing is, the simple properties are totally normal; a table’s Title column maps to that entity’s Title property, and so on. But because I’ve opted out of global automapping, there doesn’t seem to be a way to avoid mapping each of my string and integer properties on every class. I find myself wanting something like

class SomeMapping : ClassMap<SomeEntity>
{
    public SomeMapping()
    {
        MapEverythingSimple();
    }
}

Before I build something complicated that reflectively emits lambda expressions (or somesuch), am I just missing an obvious feature?

Answer 1

How about using automapping and then overrides where things don’t fit conventions?
I don’t think it’s too much of a burden. You’ll need to specify the complex relationships
that don’t fit a convention somewhere anyhow.