“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 highly recommend that Microsoft re-instate the original development team for LINQ To SQL and have them put together a release for .NET 4.0 that is placed on CodePlex as open source. There is no way the ADO.NET Team can do what is right for LINQ To SQL given their obvious bias to the Entity Framework.
I recommend the new team use a similar approach to that of the ASP.NET MVC Team where we get a highly testable, opinionated, lightweight O/R Mapper that has frequent CTP releases with attention to continuous community feedback.
Personally, I suspect improving LINQ To SQL is far easier and less resource intensive than what needs to be done to improve the ADO.NET Entity Framework. Let a new team release a LINQ To SQL version 2.0 and then leave it up to the community to continue the effort going forward if nobody at Microsoft wants to keep the project going.
Ideally, I would like to see LINQ to SQL eventually fall under the same management as the MVC Framework as I think MVC is to ASP.NET Webforms as LINQ To SQL is to the ADO.NET Entity Framework.
Just a thought