http://efvote.wufoo.com/forms/ado-net-entity-framework-vote-of-no-confidence/
maybe the Entity Framework is poised to become the "EJB" of the .NET world...
http://devpinoy.org/blogs/cruizer
cruizer: http://efvote.wufoo.com/forms/ado-net-entity-framework-vote-of-no-confidence/maybe the Entity Framework is poised to become the "EJB" of the .NET world...
Some part of the article is not correct. For example, in the ADO.Net Entity framework, lazy loading IS supported.Personally, I think that the entity framework represents a very positive first step in addressing the ORM chasm.
lazy loading is NOT supported. then again, it's not a make-or-break feature for me; there are other stuff which I don't like in the ADO.NET EF.
as for first step -- maybe it's Microsoft's first step, but the rest of the world has made its first steps years back, so why should MS have to ignore what the rest of the world has accomplished?
cruizer: lazy loading is NOT supported.
lazy loading is NOT supported.
In the ADO.NET Entity framework, it is refered to as Deferred Loading. In a way, you can see it as achieving similar goals as lazy loading.Check out http://www.singingeels.com/Articles/Entity_Framework_and_Lazy_Loading.aspx
for a discussion.Also, you can also check out http://code.msdn.microsoft.com/EFLazyLoading
for sample apps, and
http://blogs.msdn.com/jkowalski/archive/tags/EFLazyLoading/default.aspx for a series of articles that discuss the issues.
Over the years, since ADO.Net vNext was announced, and subsequently the demonstration of the Data Incubation Project, Jasper, I have seen the ADO.Net entity framework evolving, and making tremendous progress till the form it is today (in .Net 3.5 SP1). I have been eagerly following the project since ADO.Net vNext.
Indeed, many others have made their first steps many years back. While there might be features in ADO.Net EF which developers (esp those who have made use of other ORM framework) do not like, I feel that we should still see the framework in a positive light, and provide feedback to the ADO.NET team so that they can make improvements to the framework.
i guess the confusion is due to terminologies the ADO.NET EF does lazy load, but you have to explicitly load the stuff by calling .Load() (in other O/RM tools you don't need to do that; the actual loading is done transparently when you need it, sort of like J-I-T loading). for the ADO.NET EF team that is what they call "lazy loading," but others think that the real lazy loading should do away with the need for the explicit .Load() call.
the biggest thing I don't like with EF is that your entities have to derive from some class or implement some interface. that, to me, severely limits how I want my class hierarchies to evolve since we only have single inheritance with .NET. we definitely need something like the "mixin" feature of Ruby
i just hope that EF 2.0 won't be significantly different from EF 1.0 (assuming the EF team does deliver on the issues pointed out in the "no confidence" position paper). otherwise it would be better for devs to just go straight to 2.0