L2S (LINQ to SQL) or EF (Entity Framework)

Question

I am going to rebuild the existing moderate internet application that will be used for the supply chain management web solution. The core will be associated with some combinations of \ Site elements, the \ User organization, display organization-specific data (a dashboard with two Grid levels), and Drilldown, which has some complex calculations for Item transactions and a reliable grid for displaying several levels of totals, sub-calculations etc.

In the past, I developed it using ASP.Net 2.0 and ADO.Net, the backend is SQL-Server. I propose to migrate this web-based solution for the full flag MVC Architecture based on ASP.Net v3.5 and integrate other membership APIs, validation structure, etc ... it will be a complete redesign. Performance and scalability (i.e., processing millions of records, performing fast calculations, fast response times, etc.) are two main priorities. In addition, simplicity and long-term service and periodic updates at any level should also be considered.

I was wondering which of the following two would make a reliable DAL that satisfies my aforementioned requirements:

• L2S (LINQ to SQL) or EF (Entity Framework)

I searched a lot and based on this I would like to confirm my understanding:

• L2S Win98 - , , -
• EF - WinXP - , win98, , , L2S

, " " , SQL-Server . , , Entity .. , DB- Entities (, User, Org ..)..) - , ( , / VIEW). Drilldown , , , ( , )

, - , , . ! , - , "" .

, , - !

- , .

PS: : ORM-LINQ-Entity-Framework-Eric-Nelson

- LINQ to SQL vs. ADO.NET Entity Framework

- ADO.NET Entity Framework, Linq SQL

- ADO.NET Entity Framework LINQ to SQL

- LINQ to SQL Entity Framework

Answer 1

L2Sql Win98, EF Vista... , , , .

EF 4... , Windows 7 .

Answer 2

, Linq sql. , . L2S, .

DAL plinqo , Codesmith , quirks linq to sql . Oleg Sych T4, VS2008.

Answer 3

v2, .net 4.0, , linq 2 sql.

, .

v1, , , .

linq 2 sql , sql .

Answer 4

In my personal opinion, using everything you mentioned, I would use NHibernate over Linq2sql or Entity. If you are after a simple CRUD site, then the solution does not matter much, but the ability to separate the business layer from the data layer is quite difficult to implement in ADO.Net, where it is much easier (in my opinion in Nhibernate).

As I said, opinions vary greatly in this area.