Hello,

12 months ago I changed jobs and had to leave llbl behind for nHibernate. At the time I'd been quite swept up in a lot of nHibernate hype and liked the look of it's clean POCOs.

12 months later I am fed up with it. I struggle to understand how so much work could go into an ORM and yet it is riddled with absurd limitations. Its linq provider is a sad hobbled thing that needs to be put down. It's strongly typed query syntax (QueryOver) lacks any intuitive design whatsoever and has some shockers (can't select an expression!, can't join onto a subquery!!!)

I miss you llbl

That's a sad story

Sorry to hear that, Sam.... Yeah, NHibernate gets a lot of hype, but the thing with data-access technology is that it has to work always, everywhere, in all situations and shouldn't have any surprises. Though I think NHibernate isn't going forward as much as it did before, as key people left.

Your team mates, are they also fed up with NH or do they still love the random issues no-one knows how to fix?

Hi Frans,

Your team mates, are they also fed up with NH or do they still love the random issues no-one knows how to fix?

Yeh we're all a bit sick of banging our heads against Google trying to drum up answers. So often the answer is just "Oh you can't do that, try using HQL".

Though I think NHibernate isn't going forward as much as it did before, as key people left.

So what ORM do those "people" use now? Sadly we're now in too deep to change.

Not sure, though I think some moved away from .net in general and use javascript all the way now or nosql databases. I'm sure those nosql movers will be back, at least after their clients told them they want their data stored in a more generic system so it's available after the application died off

Good luck man, and I'm sure you'll be back some day

Technical support is really important to us, you don't really get that with nHibernate and you have to trawl through posts to try and find a solution. With EF you have to wait for a service pack or a hotfix (if your very lucky).