[Mono-dev] Dynamic data and Ado.net Entity set?

Atsushi Eno atsushi at ximian.com
Thu Aug 14 12:34:57 EDT 2008

Sharique uddin Ahmed Farooqui wrote:
> On Wed, Aug 13, 2008 at 7:12 AM, Atsushi Eno <atsushi at ximian.com> wrote:
>> Hello,
>> Sharique uddin Ahmed Farooqui wrote:
>>> Hi,
>>> To day MS has released sp1 of .net 3.5. which has Dynamic data,
>>> Ado.net Entity set, some improvements in Linq to Sql are the new
>>> features .
>> Where did you find "some improvements in Linq to Sql" ?
>> I thought it is discontinued, but I might be wrong.

As you didn't answer this question, I assume there is not any
improvement on Linq to SQL in fact.

(I'm not confirming you are wrong ;) If there is any improvement,
I would like to tell DBLinq guys about that.)

>>> I have few questions
>>> 1. Is there any breaking changes in Core because Sp1 oerview says
>>> "Core improvements to the CLR".
>> That question should be directed to Microsoft, no? ;-)
>>> 2. What are the plan for this features ?
>>> My guess -  for Dynamic data and Entity set we need Linq to Sql first
>> I don't think Linq to Entities depend on Linq to SQL (does it?).
>> Linq to SQL is narrow-minded "SQL Server only" technology. As Pablo
>> wrote, it is being implemented though (in DBLinq Mono mode, which is
>> somewhat wider-minded to open to some other vendors).
> Linq to sql is not and ORM, is a language feature while Entity set is
> a complete ORM solution.

Linq to SQL is not a language feature. Linq is a language feature
and Linq to SQL is just an applied technology as well as Linq to
Entities. The other difference (that Linq to SQL is not designed to
be a complete ORM while Linq to Entities is) at least brings no
Linq to SQL advantage :p

Atsushi Eno

More information about the Mono-devel-list mailing list