locked
DLINQ Support Guarantee and Length of Life Cycle RRS feed

  • Question

  • Hello DLINQ Team,

     

    I have an important question to raise. Can MS guarantee a support for DLINQ throughout the next 10 years? Will MS continue DLÍNQ even when Entity framework hits the road?

     

    Will it be guaranteed that the Framework get fixes if there are serious bugs.

     

    With MS Repository there have been a number of issues were none of them were addresses in the last 6 years and for each one the devs needed to work around.

     

    Similar things are with DataSets. There are still serious issues in the merge function that do not get adresses.

     

    Please, please please MS take the data handling serious and let us users get good support and fixes. If you have information which framework is longer to last please share with us now.

     

    Thanks

     

    Tim

    Tuesday, July 31, 2007 9:51 AM

Answers

  • Tim,

     

    This is an important question.  LINQ to SQL ships as part of the .NET Framework which follows the Microsoft Support Lifecycle for Business and Development software.  This means that it will be in mainstream support for 5 years and extended support for another 5 years. 

     

    We've provided guidance around when to use LINQ to SQL or LINQ to Entities in a post on Microsoft's data access strategy that is worth reading as well.

     

    In this first release, LINQ to SQL and LINQ to Entities are optimized around a different set of scenarios.  Longer term, we’ll look to customers to give us guidance on whether it makes sense to continue to have one stack optimized toward rapid development (LINQ to SQL), and a separate stack optimized for the enterprise (the Entity Framework), or if we should merge into a single stack.  Of course, having two stacks needs to be balanced against feature requests for each stack; the more enterprise features we add to LINQ to SQL, and the more rapid development features we add to the Entity Framework, the less compelling it is to have separate stacks.

     

    Lance Olson
    Group Program Manager
    Data Programmability

    Wednesday, August 1, 2007 1:46 AM