I need to settle these concepts in my head:
Is the Entity Framework the “new” ADO.NET? What is the difference between these two terms? And how does LINQ to SQL relate to each of them? Is it part of an entity structure?
Entity Framework is an O / R mapping module that is built on top of ADO.NET. LINQ to SQL is another O / R mapping approach, but as far as I know, Microsoft is heading to the Entity Framework in the future, not LINQ to SQL.
ADO.NET .NET Framework. , .
LINQ to SQL - , , . .NET 3.5 Framework. sql. db ADO.NET.
Entity Framework (aka ADO.NET Entity Framework) - ORM, , , db ADO.NET( - )
, LINQ 2 SQL Entity Framework ADO.NET. Microsoft (ORM). , LINQ , LINQ 2 SQL. SQL Server.
Entity Framework can be called the first true ORM from MS, which can work with all databases that satisfy SQL. The learning curve is very small if someone knows about LINQ 2 SQL. Microsoft recommends that for all future data access solutions, the Entity Framework is the perfect choice.
Hope this helps.
Source: https://habr.com/ru/post/1779394/More articles:A few "similar buttons" on the page - facebookIntelligent filter with python - optimizationSchwartz sorting example in the "Text Processing in Python" section - pythonCastle Windsor - автоматическое управление транзакциями - castle-windsoriPhone - translucent black status bar above the application - iphoneDelegate Announcement - c #Draw a stroke bar with gradient - performanceHow can I name the constructor of the parent class? - javaHaskell modules: hidden names and ghci - moduleNumber of weeks in MySQL and New Year - mysqlAll Articles