Question

I was wondering what people thought about the decision to support Entity Framework over LINQ-to-SQL? I have an application I’m developing originally in LINQ-to-SQL. I found it the perfect solution for our application.

While attempting to port to Entity Framework I was surprised how rough it was. IMHO, not even close to being ready for prime time. No lazy loading, no POCOs, horrible dependency on inheritance. I found it largely unusable in my case and instead decided to stick with LINQ-to-SQL until somehow this Entity Framework can get more polished.

Anyone else have similar experience with it?

Answer 1

That is pretty much my view. See my previous reply here. This other question wasn’t specifically about the problems in EF, but yes: it has a fair few glitches. For example (in addition to your existing options):

• no support for Expression.Invoke (re-using expression trees to form a more complex expression)
• no support for table-UDFs, which can be used to create well-defined, callable methods in the database that are still composable with sort/skip/take etc

LINQ-to-SQL handles both just fine…