Question

I am about to start a new project and am deciding what data access technology I will be using… I really like LINQ to SQL for a variety of reasons but should I start the new project using the Entity Framework instead??

I have this perception that the Entity Framework is more bloated and needlessly complicated, thus accounting for part of the reason I was thinking about going with LINQ to SQL… but as I said this may only be perception on my side as I haven’t used the Entity Framework all that much.

So which would people recommend I use for starting a new project today (note this app will be around for years to come)?

Cheers
Anthony

EDIT:
We are SQL Server shop so we don’t need database vendor independent.

Also is the generally agreed best way to abstract data access atm by using the Repository pattern which works with my domain objects?

Answer 1

LINQ to SQL is about rapid development and simplicity. If your data model is complex, or might become so, you will be better off using a more robust framework.

That said, more important than your data access tool is how well you abstract it from the rest of your code. Done right, you should be able to start with LINQ to SQL and switch when you outgrow it (or when EF 2 4 comes out).