ADO.NET Entity Framework - to use or not?

Apr 25, 2009 at 6:42 PM
Edited Apr 26, 2009 at 6:43 AM
I have spent some time today investigating ADO.NET Entity Framework, and reading articles and opinions on its usage, current status (.NET 3.5 SP1) and the future .NET 4.0/VS 2010: as far as I see this is a promising technology but it looks like it is not yet ready for enterpise level development. And what is your opinion?

ADO.NET Entity Framework

Stored Procedure Mapping

Using stored procedures with ADO.NET entity framework

ADO .NET Entity Framework Vote of No Confidence
When the Entity Framework is used on projects staffed with more than one developer, merge conflicts occur whenever two developers make changes to an entity diagram. Since the diagram tool is the default and intended tool for making changes to an entity model, the frequency of this problem is will result in an unacceptable level of friction in team member interaction and change integration.
So in short, EF as it stands now is worthless for real life use.

I guess I've wasted several weeks of my life rewriting my code for a technology that should have been released as incomplete and only in beta.
NO ONE CARES. EF is an overcomplicated piece of junk compared to L2S. If we're going to migrate our L2S DAL over to something else, it won't be Entity Framework (which you'll probably abandon next year in favor of something else anyway!)
Linq to Entities simply does NOT work in a real world environment.

Don't bother trying to use it with stored procedures that return nothing.

I have to wait for VS2010 to get something that will supposedly work?

THIS was supposed to work. You told us to move from linq to sql to linq to entities and I did all the conversions for a piece of junk that has put me weeks behind in development and still doesn't work!

I'm ready to give up and simply use an ORM that actually works and actually has support and working examples.

Why release a technology and tell us to use it when you know it is crippled?!!!!