When will linq be output in sql? Are the essential frameworks (replacement) issued yet?

Question

When will linq be output in sql? Are the framework (replacements) distributed?

Answer 1

Yes, the Entity Framework ADO.NET was released using .NET 3.5 Service Pack 3.5.

And no, the Entity Framework will not replace LINQ-2-SQL as such - they have completely different target audiences and have their own target markets.

LINQ-2-SQL is great for simpler scenarios where your business objects pretty much map your 1: 1 database tables. This often happens, and in such a scenario, EF is redundant.

EF, on the other hand, is great in an enterprise-level application where your business domain objects will not necessarily display 1: 1 on tables, or where you need to maintain multiple database databases outside of MS SQL Server.

Even with .NET 4.0, Microsoft is still investing in LINQ-2-SQL - see the Damien Guard blog post ./p>

Mark

Answer 2

Entity framework freed. LinqToSql will be updated for .Net 4 and will not go away any time soon.

Answer 3

According to the ADO.NET team at the end of last year, .NET 4.0 will become an official point when they recommend abandoning LINQ to SQL in favor of the Entity Framework.

From this blog :

“Made a significant investment in the Entity Framework, so with .NET 4.0, the Entity Framework will be our recommended solution for accessing LINQ data for relational scripts.”

Answer 4

Linq-to-SQL is a high-performance SQL server-based option. This is part of the .net structure and will not disappear. Do not pay too much attention to what comes from the lips of RDs who are trying to sell their own home ORM, or MSFT marketing ...

EF offers more abstraction and supports more databases than L2S, with the tradeoff of [much] less efficient SQL queries. Although Microsoft marketing has its own story, my personal approach is: if you are targeting SQL Server [, you want to use MSFT OR mapper], and you want scalability and performance - L2S is the technology to go for. If, on the other hand, performance and scalability are not important, but you have a team of inexperienced developers who need everything that is served on a plate, [and the person serving this plate is well versed in SSDL and CSDL manually in an XML editor] EF good rival. JMHO.