LINQ objects as business objects - pro / cons

Question

The dbml file generated by Visual Studio (sqlmetal) has objects mapped to database tables. In your opinion, are these clans suitable for use as domain model classes? Or should we avoid them and isolate them only at the data access level?

thanks

Answer 1

In most cases, the layer of sweet kindness between entity objects and SQL writing is your DAL. The whole purpose of LINQ is to provide much more expressive designs with your DAL than was possible in the past.

LINQ BL , GetCustomersByLastName(string), DAL. , , - , - BL . , DAL BL. LINQ BL DAL. DAL ; , , . true .

LINQ DAL, LINQ?

Answer 2

LINQ - . , - LINQ ( , AutoMapper, ).

, , , , . , , , Entity Framework? EF - .

Answer 3

, , . , .

, .

, , , , .

Answer 4

, .

WCF, , linq .

, xml- (, , ).

LINQ, , . , , .