An update on LINQ Entity Framework interview
David Sceppa provided me some updated answers to my questions from other members of his team. Thank you David for taking the time to follow through on this great information. You may want to read the original blog entry first. Q: Will one or the other be dropped in the future? (referring to LINQ to SQL and Entity Frameworks) UPDATE:There are no plans to drop support for either technology. 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. The ADO.NET Entity Framework will roll into an update of the .NET Framework in the first half of 2008, and will be covered by the Microsoft Support Lifecycle as well. Q: When can we expect to receive a new SDK for the VS 2008 beta 2? UPDATE:Beta 2 of the ADO.NET Entity Framework, which you can use in conjunction with Visual Studio 2008 Beta 2, is now available. You can download the latest here. You can download the first release of the Entity Framework Tools here. (Note: Despite the different terminology [August CTP vs. Beta 2] this release of the tools is intended for VS 2008 Beta 2) Q: Will the ADO.NET Entity Framework ship with VS 2008 or after? UPDATE:Because the Entity Framework is more robust in terms of mapping flexibility and ability to work with 3rd party ADO.NET Data Providers, we felt we needed one more development milestone and round of feedback to complete the project and address key customer requirements, including a visual designer for entities. While we understand concerns around deployment of the Entity Framework after the release of the core .NET Framework 3.5, we felt that it was important not to delay other valuable innovations of Orcas, such as LINQ itself (including LINQ over in-memory objects, LINQ over XML documents, LINQ over DataSet, and direct mapping of LINQ against Microsoft SQL Server schemas through LINQ to SQL). We plan to ship the ADO.NET Entity Framework in the first half of 2008 as a recommended update to the .NET Framework 3.5 that will be included in future service packs or full releases of the .NET Framework. blog postQ: Will it (LINQ Entity Framework) be an add-on (like WSE) or included in a SP? A lot of people are concerned about this, citing that WSE has not been included in a lot of their projects because it is a separate install from .Net and some IT admins won’t allow it to be installed – So they are concerned that the Entity Framework as an add on will hurt adoption. UPDATE: We plan to ship the ADO.NET Entity Framework as a recommended update to the .NET Framework 3.5 that will be included in future service packs or full releases of the .NET Framework.
Similar Posts
- An interview with David Sceppa about the LINQ Entity Framework
- The first 120 days…
- Looking ahead to 2008, and back at 2007