none
linq to sql future? RRS feed

  • Question

  • as I dig more deeply into linq to sql, I've been reading on several forums that MS is killing the project and that it won't be updated.  Is this true?  Can anyone from Microsoft speak to this?  I really like linq to sql but I don't want to waste a lot of time on it if it's not going into the future.
    Monday, January 5, 2009 10:14 PM

Answers

  • The following articles from redmond developer news may be of interest to you:

    http://reddevnews.com/blogs/weblog.aspx?blog=3009 - Data Access Shakeout: What's A DB Developer To Do?
    http://reddevnews.com/blogs/weblog.aspx?blog=3036 - Microsoft Says LINQ to SQL Not Dead
    http://reddevnews.com/blogs/weblog.aspx?blog=3016 - Digital Darwinism

    In short: Linq-to-SQL is not going away but [they say] they're planning to spend more time on adding features into EF.

    That said, L2S is here today and it works very well. There are some minor bugs and it would be nice with more features but I have not yet encountered anything that does not have a workaround.

    Any 'alternative' technologies (such as EFvNext) are not yet here yet so if you're writing code today and want to use an ORM solution from Microsoft I would say: stick to L2S for now and re-evaluate in the future when they release an alternative.

    (Also keep an eye on the reorg rumours - who knows what effect that could have on yet-to-be-released stuff like EFvNext)
    Tuesday, January 6, 2009 1:04 AM
    Answerer

All replies

  • The following articles from redmond developer news may be of interest to you:

    http://reddevnews.com/blogs/weblog.aspx?blog=3009 - Data Access Shakeout: What's A DB Developer To Do?
    http://reddevnews.com/blogs/weblog.aspx?blog=3036 - Microsoft Says LINQ to SQL Not Dead
    http://reddevnews.com/blogs/weblog.aspx?blog=3016 - Digital Darwinism

    In short: Linq-to-SQL is not going away but [they say] they're planning to spend more time on adding features into EF.

    That said, L2S is here today and it works very well. There are some minor bugs and it would be nice with more features but I have not yet encountered anything that does not have a workaround.

    Any 'alternative' technologies (such as EFvNext) are not yet here yet so if you're writing code today and want to use an ORM solution from Microsoft I would say: stick to L2S for now and re-evaluate in the future when they release an alternative.

    (Also keep an eye on the reorg rumours - who knows what effect that could have on yet-to-be-released stuff like EFvNext)
    Tuesday, January 6, 2009 1:04 AM
    Answerer
  • I havne't used either that much, but from waht I see so far, I strongly prefer the l2s.  The entity thing seems like a real pain in the butt.
    Tuesday, January 6, 2009 9:27 AM