Should I consider LINQ for Entities?

I am just starting with the Microsoft stack building a website in ASP.Net MVC and still using LINQ to SQL. Should I consider LINQ for Entities? Is there anything special? If so, then what?

+4
source share
5 answers

I myself studied this thing.

Here are my conclusions in a nutshell

LINQ to SQL

Benefits

  • Incredibly easy to use

disadvantages

  • Unable to update the chart from the database, you need to remove your class and then drag it back onto the chart from the database. This is a real pain if you altered the chart at all.

  • Not actively developed (they will develop the Entity Framework instead).

Entity Framework

Benefits

disadvantages

  • Sophisticated and much less intuitive

Conclusion

I personally decided to go the way of using the Entity Framework. I bought a book and read online material, and I am very impressed with it. It took a little extra effort to learn, but the benefits are really great.

+8
source

Here is an article describing the differences between the two:

http://dotnetaddict.dotnetdevelopersjournal.com/adoef_vs_linqsql.htm

+1
source

here is a little comparison of the two, there are pros and cons for both.

http://dotnetaddict.dotnetdevelopersjournal.com/adoef_vs_linqsql.htm

+1
source

First, Linq offers a lot of functionality for the entity.

Secondly, Microsoft will put more time in it.

and I'm sure many other good reasons

0
source

Although LINQ to SQL is not going to go away, Microsoft is betting on LINQ to Entities. For this reason, I would go with LINQ in Entities.

The ADO.NET team blog has more information about the problem:

http://blogs.msdn.com/adonet/archive/2008/10/29/update-on-linq-to-sql-and-linq-to-entities-roadmap.aspx

http://blogs.msdn.com/adonet/archive/2008/10/31/clarifying-the-message-on-l2s-futures.aspx

I listed these notes in chronological order, but I definitely read at least the last one - in fact, this is the most important.

0
source

Source: https://habr.com/ru/post/1286622/


All Articles