Andres Aguiar's Weblog

Right here, right now

DLinQ = LinQ for SQL

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.

Now, does this make sense? How will someone decide to use one or the other?

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.

 

Posted: Jun 12 2006, 12:34 PM by aaguiar | with 14 comment(s)
Filed under: , , , ,

Comments

David Hayden - Florida .NET Developer - C# and SQL Server said:

# June 12, 2006 2:57 PM

Linq in Action News said:

Some of you may have read the documents on ADO.NET 3.0 and the Entity
Framework when they were published,...
# June 12, 2006 7:27 PM

Fabrice's weblog said:

Some of you may have read the documents on ADO.NET 3.0 and the Entity
Framework when they were published,...
# June 12, 2006 7:27 PM

Todotnet Blog said:

# June 13, 2006 2:42 AM

Todotnet Blog said:

# June 13, 2006 2:45 AM

Thomas Lebrun said:

Si vous travaillez avec DLINQ, voici un post qui devrait vous intéresser:
http://weblogs.asp.net/aaguiar/archive/2006/06/12/DLinQ-_3D00_-LinQ-for-SQL.aspx...
# June 13, 2006 2:59 AM

FransBouma said:

I also don't understand why they put out 2 different flavors. But I don't know the details of any of the new types, so I can't comment on that (I'm not at teched)

What it will create though is a lot of confusion for the developer: he has a database to talk to and some code to write: what to use? Linq for Sql or the entity framework?

Is it even possible to make that decision? Based on the info I have on both frameworks, I don't think it is. So I predict one of the two will never make it to the final release, for the simple fact that whatever you can do with DLinq is also possible with the entity framework.
# June 13, 2006 5:01 AM

Wooley's Wonderings said:

As is typical at Microsoft conferences, they have a way of announcing code name changes. Yesterday, they...
# June 13, 2006 2:15 PM

STEFANO DEMILIANI WeBlog said:

# June 14, 2006 2:51 AM

Data Access blog said:

Since announcing our ADO.NET vNext plans at TechEd last week, the team has been on the lookout for your...
# June 24, 2006 12:50 AM

ADO.NET team blog said:

(this post was originally posted here) Since announcing our ADO.NET vNext plans at TechEd ...

# July 11, 2006 1:34 PM

James Schementi said:

linq is actually the technology that dlinq is build on-top of.

# July 31, 2006 12:21 AM

Paul Gielens:ThoughtsService said:

David and Andres speculated on the positioning of the upcoming mapping technologies in .NET.The problem

# August 15, 2006 5:25 PM

Paul Gielens:ThoughtsService said:

David and Andres speculated on the positioning of the upcoming mapping technologies in .NET.The problem

# August 15, 2006 5:26 PM