The End of LINQ To SQL?

October 31, 2008

The End of LINQ To SQL?

Today I read a fewThe End of LINQ To SQL?
blog posts that were
published regarding 
the announcement
on the ADO.NET Team Blog

(David Hayden, Oren Eini 
and more).
That announcement included the following lines which made everybody furious:
”We’re making significant investments in the Entity Framework such that
as of .NET 4.0 the Entity Framework will be our recommended data access
solution for LINQ to relational scenarios.  We are listening to customers regarding
LINQ to SQL and will continue to evolve the product based on feedback we receive
from the community as well.”.  
I share the same thoughts as David Hayden expressed in his post. I think that if
Microsoft is going to abandon LINQ to SQL, they should publish the framework on
CodePlex and let the community continue the development effort.
This way the people that started using LINQ to SQL in the last year
will have a support for that framework and won’t have to change all their data
access because the framework is legacy. Also, LINQ to SQL will continue to be
a light weight alternative to the Entity Framework like other open source frameworks
(NHibernate, SubSonic, Castle ActiveRecord and more).
If you think like the other community members and also like I do, write about it and
show that you care.

Add comment
facebook linkedin twitter email

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>



  1. Bob SaggettOctober 31, 2008 ב 13:29

    Can anybody actually point me to the announcement where Microsoft say they are dropping Link to SQL? All I can see is an announcment saying that MS would prefer you to use EF.

    I would prefer to have a Ferrari over a Nissan but that’s not going to stop me driving the Nissan.

  2. Gil FinkNovember 1, 2008 ב 3:08

    Hi Bob Saggett,

    As someone that know Microsoft for years, you only need to read between the lines to understand that LINQ to SQL is going to be turned into legacy. I had that experience in the past when I used CMS server of Microsoft and in the end they turned it to legacy because sharepoint server was out. You can read the things that David Hayden wrote in a follow up post yesterday:…/linq-to-sql-is-dead-read-between-the-lines.aspx.

  3. Gil FinkNovember 2, 2008 ב 1:22

    Hello everybody,

    Tim Mallalieu, the program manager of LINQ to SQL and LINQ to Entities, posted a clarifying post that in other words say what I wrote earlier this week – LINQ to SQL is about to be come legacy. You can read it here:…/clarifying-the-message-on-l2s-futures.aspx

  4. Bob SaggettNovember 3, 2008 ב 12:08


    I also have worked with Microsoft for many years. I agree that this clearly is a decision to move L2S into legacy but this really is not the same as L2S being dead.

    Dead for me would equate to “Not available in future versions of the framework”. This announcement does not sugegst that this is the case.

    Reading some of the rather excitable blog posts on the web at the moment on this topic, you would assume that your applications were about to die!

  5. Gil FinkNovember 3, 2008 ב 14:55

    Hi Bob,
    I didn’t indicated that L2S is dead. I did wrote it is going to be legacy which means that it’ll keep on living in the framework but there won’t be a technical support for the technology and also no bug fixes in the future. That is really bad for projects that use the technology which will be forced to re-design their solution. This is why I share David Hayden’s suggestion to move the project to codeplex as an open source.