I've been hearing a lot of rumors coming out of TechEd that Microsoft is going to be releasing two O/R Mappers, DLINQ (Linq to Sql), and Linq for Entities. Please tell me this isn't true! We already have too many O/R Mappers, let's not make it so Microsoft has too two many as well!
http://steve.emxsoftware.com/ORMappers/As+if+we+need+more+OR+Mappers
- Steve
Two O/R Mappers from Microsoft? Say it ain't so!
Hot Topic
Visual Studio
- SourceSafe auto create sub-structures?
- Select a Range by a Cell
- Control inside a control
- Master detail, why doesn't the contents of a frame 'inherit' the datacontext?
- Using SDk with VS2003
- [BUG] BitmapEffect clipped output
- WinForms Interop, Drag & Drop from WPF -> WinForms
- problem with ProgressBar
- What could the ERROR be
- No data in Reports, but the headers show up fine
Two O/R Mappers from Microsoft? Say it ain't so!
Soe
bbossi
I believe the original source of the rumor is at http://weblogs.asp.net/aaguiar/archive/2006/06/12/DLinQ-_3D00_-LinQ-for-SQL.aspx. I skimmed the Ado.Next document before it was pulled and was not impressed with what I saw from the entity side. Exactly how LINQ and ADO.Next work together may well be the key to whether it succeeds or fails. It could well be that DLINQ would focus on 1-1 entity/table mappings where-as Linq for Entities would work for more object heirarcharies, but this is mere speculation. At this point there are more questions than answers. I look forward to responses from Matt and the other insiders on the unified data vision.
Jim Wooley
http://devauthority.com/blogs/jwooley/archive/2006/06/13/1322.aspx
gurpreet11
Kind of true - I am here at Tech Ed and went down and talked to the LINQ and ADO.NET 3.0 folks. They are working together on these capabilities and the end result is still up in the air - they aren't sure if the two will merge or if they will remain separate, but they will not compete with each other. Linq to Sql is not as "expressive" or as flexible as EDM (Linq to Entities).
The Linq to SQL is direct and has less ability to abstract the object model from the database. EDM has a richer ability to model objects different from how the DB represents them. I was really worried about this after this morning's session on Linq (although the session was awesome and I am super excited to use Linq), but after talking to the people in the Technical Learning Center (TLC) I am not worried - obviously that is trusting them to do the right thing, but the fact that they are communicating (as evidenced by the Linq to Entities capability) gives me confidence that they will figure it out.