Comments on: The Entity Framework Team are Real Professionals

By: Szindbad

Szindbad — Wed, 01 Oct 2008 09:21:41 +0000

… ah forgot some: Workflow designer files, Winforms designer outputs, binary resources (pictures), office documents (!), pdfs, application configurations, class designer files, reports, stylesheets, etc.

I simply agree with you, i will simply not use any of these becasue issues with version control.

By: Szindbad

Szindbad — Wed, 01 Oct 2008 09:07:24 +0000

oh, man. The same version control issue arises with project file (metadata), solution file (metadata), resources (resx, metadata), statically typed datasets (metadata).

Now you can scream and jump!

By: David Fauber

David Fauber — Mon, 30 Jun 2008 15:11:01 +0000

“I distrust with the concept that anyone who hasn’t experienced something just can’t get it.”

That was my favorite, sounds like the project manager mantra. But hey, they probably stayed at Holiday Inn last night.

By: Dew Drop - June 29, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - June 29, 2008 | Alvin Ashcraft's Morning Dew — Sun, 29 Jun 2008 11:59:58 +0000

[...] The Entity Framework Team are Real Professionals (Jan Van Ryswyck) [...]

By: Jan Van Ryswyck

Jan Van Ryswyck — Sat, 28 Jun 2008 10:29:30 +0000

If the EF makes it difficult, then its most certainly not encouraging source control. If source control is difficult to use with a certain technology, then developers tend to go with the technology and not source-control.

I’ve seen this happen with Microsoft Dynamics. Same story there. Instead of ditching the technology, source control got thrown away. If this is what we get from Redmond after 30 years of IT evolution, then it’s simply unacceptable.

Then for me the EF practically excludes source control this way. Why is it then that numerous other ORM solutions out there can get this one right from the first time. As I mentioned in my post, it’s simply a matter of getting the priorities straight. Supporting OO principles and source control are one of those priorities, otherwise it is a useless piece of technology.

I can only recommend to step outside the narrow Microsoft vision, and have a look at other solutions like NHibernate, IBatis or another non-intrusive data solution. When I mean that the EF team are real professionals, then I also mean that the NHibernate contributors are gods!

I want to say kudos the people who started this whole “vote of no confidence” initiave. They are the ones who aknowledge that something has to change in the .NET space, especially regarding some Microsoft products. The ALT.NET community are the only ones I know of. So instead of bashing this initiave, lets improve the way we want to write software for a change.

By: Kathleen Dollard

Kathleen Dollard — Fri, 27 Jun 2008 23:05:29 +0000

Of course source control is a non-negotiable.

EF does not exclude the use of source control. It makes it difficult because of more frequent collisions than desirable.

The list you quoted from is my summary of the vote of not confidence petition, stating my opinion that none of these things make EF a faiure.

Data-centric designs in the sense of EF and VB6 are quite different animals as I’m sure you’re aware. Mapping is a non-negotiable. EF provides it, although it clearly has issues.

Metadata is a point of source control collisions. That’s not an easy problem to solve.

Kathleen