Clarifying the message on L2S Futures.
There has been a variety of responses to the post on L2S futures in the last couple of days.
Let me start by saying sorry for the radio silence since the post but, as Elisa mentioned, we posted it while at PDC and were focusing on the interactions there over the last couple of days.
There are a couple specific points that I would like to clarify:
Is LINQ dead?
No… heck no…
There is a big difference between LINQ to SQL and LINQ.
LINQ is Language Integrated Query, today we ship the following sources over which one can execute a LINQ query:
- DataSet : LINQ to DataSet
- XML: LINQ to XML
- In Memory Objects: LINQ to Objects
- ADO.NET Data Services (Astoria) Client: LINQ to Data Services
- LINQ to Relational Databases:
- LINQ to SQL – the technology we were discussing in the original post
- Entity Framework (LINQ to Entities)
There are many other people in the company and broader community working on LINQ solutions to other data sources. We are also excited to see LINQ being applied to many cool new problems beyond the typical data access scenario.
The discussion in the post was about the difference in investment level that we will have going forward regarding LINQ to SQL and the Entity Framework. LINQ itself, is a fundamental technology that we will continue to bet heavily on.
So what exactly is the announcement about?
Over the last few months we have been looking at how to carry forward LINQ to SQL and LINQ to Entities. At first glance one may assert that they are differentiated technologies and can be evolved separately. The problem is that the intersection of capabilities is already quite large and the asks from users of each technology takes the products on a rapid feature convergence path. For example, common asks for LINQ to Entities (that are being delivered with .NET 4.0) are POCO and Lazy Load. Similarly, in the LINQ to SQL side we are being asked to provide new mapping strategies and other features which the EF already has. Additionally there are common asks for new features like UDT’s and better N-Tier support for both stacks. The announcement really centers around the point that, after looking hard at this and triangulating with internal partners and customers, we decided to take the EF forward with regards to the overall convergence effort and over time provide a single solution that can address the various asks.
Is LINQ to SQL Dead?
We will continue make some investments in LINQ to SQL based on customer feedback. This post was about making our intentions for future innovation clear and to call out the fact that as of .NET 4.0, LINQ to Entities will be the recommended data access solution for LINQ to relational scenarios. As mentioned, we have been working on this decision for the last few months. When we made the decision, we felt that it was important to immediately to let the community know. We knew that being open about this would result in a lot of feedback from the community, but it was important to be transparent about what we are doing as early as possible. We want to get this information out to developers so that you know where we’re headed and can factor that in when you’re deciding how to build future applications on .NET. We also want to get your feedback on the key experiences in LINQ to SQL that we need to add in to LINQ to Entities in order to enable the same simple scenarios that brought you to use LINQ to SQL in the first place.
Program Manager, LINQ to SQL and LINQ to Entities