LINQ to SQL or Enitity Data Model for asp.net MVC 3 application

Question

I have been architecting big database application using asp.net mvc 3 technology. Please clarify me whether to go with LINQ to SQL or EDM.

Thanks in advance

Damodar

Answer 1

On 9/20/2011 10:48 PM, damodarp wrote:

> I have been architecting big database application using asp.net mvc 3

> technology. Please clarify me whether to go with LINQ to SQL or EDM.

>

 

Linq-2-SQL is just a Linq solution while EF is a robust ORM solution. I

wouldn't dare use Link-2-SQL in an enterprise level ASP.NET solution on

the back-end. Also, I wouldn't use Linq-2-SQL on the back-end of any

enterprise level SOA solution using WCF either.

 

<http://dev.vnc.in/linq2sql-or-entity-framework.html>

<http://blogs.msdn.com/b/adonet/archive/2009/08/05/improvements-to-the-generated-sql-in-net-4-0-beta1.aspx>

<http://www.develop.com/entityframework4>

<http://www.ef-faq.org/performance.html>

<http://blogs.msdn.com/b/alexj/archive/2009/03/26/index-of-tips.aspx>

<http://msdn.microsoft.com/en-us/library/bb387145.aspx>

<http://msdn.microsoft.com/en-us/library/cc853327(v=vs.90).aspx>

<http://weblogs.asp.net/scottgu/archive/2010/07/16/code-first-development-with-entity-framework-4.aspx>

  

Answer 2

On 9/20/2011 10:48 PM, damodarp wrote:

 

<snipped>

 

I left out the tips and tricks.

 

<http://blogs.msdn.com/b/alexj/archive/2009/03/26/index-of-tips.aspx>