Personally I think it is better to use an ORM like the entity framework for your data access because it converts your database tables to strongly typed classes. Strongly typed classes decrease the likelyhood of you putting the wrong type of data in a database
field.
For most trivial cases, yes. Although using much simpler mini-ORMs like Massive, Dapper, Simple.Data can be more lightweight than a full blown ORM like EF or nhibernate. If you do use an ORM, be very careful that you don't let it control your project. I've
seen projects turn into nhibernate or EF fan-idols and the whole project being built to service those tools rather than the other way round. They're great tools with immense power but with great power comes greater responsibility.
Ken Tucker
Of course without knowing anything about the project it impossible to recommend which is better in this case
Couldn't agree more...it's a case of "it depends" and "right tool for the job".
"If I can see further than anyone else, it is only because I am standing on the shoulders of giants."blog: www.heartysoft.com twitter: @ashic
Marked as answer by HeartattacK on May 28, 2011 08:13 AM
HeartattacK
All-Star
55262 Points
5917 Posts
Moderator
MVP
Re: EntityFramework or ADO.NET
May 24, 2011 10:07 AM|LINK
For most trivial cases, yes. Although using much simpler mini-ORMs like Massive, Dapper, Simple.Data can be more lightweight than a full blown ORM like EF or nhibernate. If you do use an ORM, be very careful that you don't let it control your project. I've seen projects turn into nhibernate or EF fan-idols and the whole project being built to service those tools rather than the other way round. They're great tools with immense power but with great power comes greater responsibility.
Couldn't agree more...it's a case of "it depends" and "right tool for the job".
blog: www.heartysoft.com
twitter: @ashic