Linq vs MS Enterprise Library DAAB

At work, we just upgraded from VS2005 to 2010. At this point, we used only sprocs (I think, out of habit, more than anything). I play with Linq (very simple tutorials - nothing serious). As my first experience with ORM, I like it.

In addition, I recently met with the Enterprise Library blocks. Generally speaking, will the project use either ORM or DAAB, or can it potentially use the project for both? Does it depend on the situation or just on preference? Are there any cases when one option is better than another?

Thank.

+3
source share
3 answers

... DAAB , LINQ to SQL ADO.NET EF , , DAAB ADO.NET(DataSet ..).

LINQ, , LINQ ( LINQ ).

, LINQ; DAAB, code-gen.

.

+1

, DAAB 2.0 4.1. FWIW ( Pro ORM):

:

  • - POCO ( LINQ2SQL), EF4 POCOs, - .
  • / , , , ( SPROC)
  • , "" . LINQ2SQL "SavesWith" "LoadsWith"

, ORM 80% /, , .

+2

DAAB (, DataSets), ORM, Linq, , .

DAAB, (IIRC ), , .

ORM . " - ", , - , , - - . "", , , .

DAAB. (Unity!) EL . , . ORM , . Linq to Sql , EF4 . , nHibernate, .

, EF4 code-first bits, . , , ; EF4 ...

+1

Source: https://habr.com/ru/post/1756573/


All Articles