Why use the Entity Framework?
There are a number of places where you can read an introduction to the Entity Framework, listen to a podcast about it, or watch a screen cast or video of an interview. Even with these various resources, though, there are so many different data access technologies out there that it’s not uncommon for me to get the question: Why should I use the Entity Framework? Or what differentiates it from other options like just using ADO.Net SqlClient and friends, LINQ to SQL or something like nHibernate? I like the second question better, because the truth is that different problems merit different solutions. So here’s just a quick take on my perspective about these: Entity Framework vs. traditional ADO.Net All of the standard ORM arguments apply here. The highlights are that you can write code against the Entity Framework and the system will automatically produce objects for you as well as track changes on those objects and simplify the process of updating the database. The EF can therefore repla
Related Questions
- In phase A of the conceptual framework project, the boards propose to adopt the entity perspective - what does this mean for the parent company approach to consolidated financial statements?
- Why does LINQPad use LINQ to SQL under the covers, rather than Entity Framework?
- Is Entity Framework supported with SQL Azure?
