by fmarguerie via Fabrice's weblog on 6/13/2006 5:18:00 AM
Some of you may have read the documents on ADO.NET 3.0 and the Entity Framework when they were published, before they were promptly removed. The big question since that time has been: What will happen to DLinq in regard to the future of ADO.NET, which seemed to offer the same services and more with a different solution? Well, Andres Aguiar has the scoop, live from TechEd in Boston: apparently both frameworks will be kept.
OK, it actually happened. We'll have two mapping technologies in .NET v.next. LinQ for SQL, previously known as DLinQ is the 'simple' mapping technology. LinQ for Entities, will be on top of the new ADO.NET Entity Framework, and will be the 'complex' (we could say 'real') mapping technology.
I think Microsoft did this for internal politically correctness (they did not want to not to ship any of the frameworks) but I can't see why this is good for the .NET Framework as a whole.
Original Post: Bye bye DLinq, Hello Linq for Sql and the ADO.NET Entity Framework!
The content of the postings is owned by the respective author. CSharpFeeds is not responsible for the contents of the postings. This site is automatically generated and cannot be reviewed for abusive content. If you find abusive content on CSharpFeeds, please contact us. Designated trademarks and brands are the property of their respective owners. All rights reserved.
