When to use "Linq to sql"?

Question

What is pro and con for using Linq to SQL technology and ADO.NET core technology for access databases?

Answer 1

Advantage

• You do not need to create business objects. Dbml files will do for you
• No need to worry about writing queries because linq2sql converts your statistics into efficient queries
• Important Lazy Loading Related Objects

Disadvantage

• Disabling linq is not supported. If you cannot remove objects from the DataContext object. for more details: The most efficient way to upgrade from LINQ to SQL

Answer 2

I have the same point of view as this post, I have not yet found serious Linq flaws.

I created a number or application and websites using Linq, and found it extremely easy to use

http://forums.asp.net/t/1520157.aspx comment from BoogleC

Sp relationship

Answer 3

The identifier must also be careful in how you write the LINQ statement. Sometimes it’s better to compile Linq, rather than the way each individual Linq query is fully parsed every time this happens. See below linq

http://www.codinghorror.com/blog/2010/03/compiled-or-bust.html

Answer 4

I would not recommend LINQ to SQL at all, since it is effectively dead (you do not want to write legacy code, right?). Microsoft is no longer developing it, and they recommend using the Entity Framework instead (see here ); however, if you are interested in using ORM , I highly recommend looking at NHibernate .