I found that whether the Strong-typed TableAdapter，or LINQ or EF……Microsoft is always fixing the CRUD methods with model classes together……Why don't create layer cs files so as to seperate CRUD methods from model classes together in different namespaces？That'd
be OK and easy for Microsoft……
PS：This isn't a question about real EF or LINQ or a ADO.NET，What I'm intersted in is Why they are designed like this？SO THIS IS A DESIGNING QUESTIO，PLEASE DON'T MOVE THE THREAD TO ADO.NET, LINQ OR EF PART！
TimoYang
Contributor
3732 Points
1275 Posts
Why does Microsoft combine the logic methods with Model classes together？
Jan 02, 2012 02:57 AM|LINK
I found that whether the Strong-typed TableAdapter，or LINQ or EF……Microsoft is always fixing the CRUD methods with model classes together……Why don't create layer cs files so as to seperate CRUD methods from model classes together in different namespaces？That'd be OK and easy for Microsoft……
PS：This isn't a question about real EF or LINQ or a ADO.NET，What I'm intersted in is Why they are designed like this？SO THIS IS A DESIGNING QUESTIO，PLEASE DON'T MOVE THE THREAD TO ADO.NET, LINQ OR EF PART！