I went through this same process recently. I ended up choosing NHibernate, however , I'm running the trunk version of it for the better Linq support. + FluentNHibernate (both of which are easy to build)
I found EF ok, certainly has some easy to use tooling for quick and simple stuff, but for legacy databases, which is what I'm dealing with, NH seems a lot more flexible. Documentation for NH is a bit tricky....as soon as you are off the main track, not a lot of people can help you, but usually somewhere in some corner of the internet, someone has come across the same problem and has worked around it. It can take some time tracking this kind of info down though. Overall I think NH is probably a better bet for the next little bit.... but you aren't going to go seriously wrong with either choice Regards, Keith On Wed, Jun 9, 2010 at 3:58 AM, Red Tiger <[email protected]> wrote: > We're in the process of choosing an ORM, and we're looking at either > NHibernate or Entity Framework. Please don't take this question the > wrong way, but how does the future of NHibernate look? Will it > continue to be supported by the very intelligent developers who have > made it what it is today? > > Thank you! > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
