How is Entity Framework 4's POCO support compared to NHibernate?
Posted
by Kevin Pang
on Stack Overflow
See other posts from Stack Overflow
or by Kevin Pang
Published on 2010-04-15T17:55:31Z
Indexed on
2010/04/15
18:13 UTC
Read the original article
Hit count: 535
Just wondering if anyone has had any experience using Entity Framework 4's POCO support and how it stands up compared to NHibernate. If they're the same, I'd be very interested in making Entity Framework 4 my ORM of choice if only because it would:
- Support both data first AND object first development
- Have a robust LINQ provider
- Be easier to pitch to clients (since it's developed by Microsoft)
- Come baked into the .NET framework rather than requiring 8 dlls to get up and running
In other words, are there any major shortcomings to EF4? Does it support all of the basic functionality NHibernate supports (lazy-loading, eager-loading, 1st level caching, etc.) or is it still rough around the edges? Is the syntax for setting up the mappings as easy as NHibernate and/or Fluent NHibernate?
Edit: Please don't bring up the vote of no confidence. That was ages ago and dealt with some serious shortcomings of EF1 that really don't seem to apply anymore to EF4.
© Stack Overflow or respective owner