Geek Answers Handbook

Is the Entity Framework a more than very time-consuming way to save some time?

I got two chapters on a 1000+ page in the entity structure and got discouraged and reverted to the old old stored procedures.

What is consensus (if any) in the Entity Framework? It would be interesting to hear from people who have completed EF-based projects to see if they think it's worth the effort.

I worked a bit with the T4 templates and found a way to generate my SPROC and DTO just the way I like, without messing with EF. Did I miss something?

+5
source share
4 answers

LINQ, Entity, ORM SQL- .

, - -, , , , , , , .

+2

T4 SPROC DTO , , EF. - ?

. , , ORM.

Entity Framework , T4:

  • Microsoft
  • .

EF , , , , . , , .

+2

, ORM. , , , ORM, EF NHibernate.

API, , , , , . , .

+1

CRUD Entity Framework ORM . , . , , , , -, . ORM .

sproc ? ( T4 ), / ? , ORM , , .

- ( , CRUD) sprocs ? ORM - , , .

I have done it both ways, and T4 leaves much to be desired as a solution for the data layer.

Even with ORM, there are scripts (for performance or something else) where you will use sprocs, and that's fine, but you may need no more than a few sprocs for a database with hundreds of tables.

ORMs offer many features that you may not need today, but you will be happy that you do not have to create them yourself when you need them.

0
source

More articles:


All Articles