Entity Framework 4.0 vs Application Data block

Question

1.00/5 (1 vote)

See more:

What are the advantages and disadvantages of Entity Framework 4.0. What are best scenarios and cases where we should use EF 4.0. Many Experts including Martin Fowler hates ORM , what's your say on this ?

Do you prefer using Microsoft Enterprise Data Block over EF 4.0 ? There is lot of ambiguity while design your application and decide what to use while writing your DAL (data Access layer).

Posted 26-Jan-15 9:32am

shiv Mohan

Add a Solution

Comments

Richard Deeming 26-Jan-15 15:57pm

You've been a member for over 9 years. That should be long enough to realise that we don't like reposts[^]!

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

**Zoltán Zörgő** · Answer 1 · 2015-01-26T10:18:00

Entity framework is evolving. So, I really don't prefere Entity Framework 4... when there is Entitty Framework 6. If one hates ORM, than he/she has a subjective attitude, which is out of any objective question. There are better and less good ORM implementations, but hating them... why?

Still, if you are assessing the design considerations of your project, you need to consider objective aspects. One major difference between DAAB and EF is the approach to the data. EF (and ORMs in general) makes model strongly typed thus makes it part of your OO code - and you have Linq! DAAB is using a legacy approach. So if you want to have a neat code less work during the whole lifecycle, choose EF. If you need performance, and you want a low level control over the executed SQL code, choose lagacy tools and DAAB. Still the difference in performance is not that much...

Consider reading this performance comparison: http://serena-yeoh.blogspot.hu/2014/02/entity-framework-vs-el-daab-performance.html[^] but this too: http://serena-yeoh.blogspot.hu/2014/02/entity-framework-6-vs-el6-daab.html[^]