I have heard some bad things about the Entity Framework, and I am considering using it.
If you have never used any business object or O / RM (for example, NHibernate or LLBLGen), you probably will not find many shortcomings in the Entity Framework. In my company, we evaluated all 3 tools and decided to choose LLBLGen, because it was a very simple way to work directly with the database (rather than spend a lot of time creating an object model).
- ( LLBLGen EF), , NHibernate. "" Entity Framework... , LLBLGen.
... 3 , EF NHibernate .
:
, sql, .. . .
Entity Framework ORM, .
Entity Framework:
, , .. ( , Micorsoft )
IMHO, .
, , ? , .
" -". . SQL, , .., , SP. (, ..), ? , . , .
, - Entity Framework , .
, , , SQL DAL.
, , , , , ( ), . . , , , .
fooobar.com/questions/tagged/... .
Entity Framework 4. - concurrency. Entity Framework: - -, - , - - ( CRUD, , )
, , ORM: , .
Michel - concurrency ? EF , - . ORM (LLBLGen), @MS native ORM EF. .
: http://msdn.microsoft.com/en-us/library/aa697427(VS.80).aspx
: , EF , , , . / , , , ... , , , , .
10 , , ive:
• ? - 4, -, ORM.
• ? - -, . . .
• ? - VS
• ? - , ORM . LLBLGen 4 . , , - , , .
Im, + , .
FK EF , .
Microsoft, in my opinion, is misconfigured. The result of encouraging Developers (especially beginners) to use EF instead of learning SQL is that it ends up with poorly developed applications with potential performance losses. I have seen that C # code extends over 200 lines that could be written in 3 lines of SQL.
This is the main problem that I see in O / R Mappers, lack of understanding of SQL. Call me at the old school; -)