实体框架 – MVC3应用程序/服务层/存储库层/ POCO类/ EF4 – 问

Are view models DTO’s?

可以被认为是控制器和视图之间的一种数据传输对象。

Should they contain just simple properties like Name,AddressLine1,Address City,etc,or should they contain complex properties,multiple objects,etc.

理想的简单属性，但也可以聚合其他视图模型，但没有模型(例如：EF模型)。

Is the validation in the view model.

有两种类型的验证逻辑：进入服务层的业务验证(例如用户名已经存在)，进入视图模型的UI验证(例如：username)。

Can the view models just contain the POCO classes returned from EF,or should I be using the AutoMapper?

没有EF在视图模型。视图模型是具有简单属性和其他复杂属性的POCO类，指向其他视图模型。他们还可以包含方法，以便正确格式化将在特定视图中呈现的数据，这些模型将用于此类数据。

If using AutoMapper and DTO,are DTO’s clones of the POCO classes?

不知道我明白这个问题。

Would you map in the controller,view model,or in the service layer below?

控制器。

To me,the service(s) are objects that contact the repository(s) to get POCO objects back from the EF. This is where all of my business logic is. Once the service hands an object back to a repository to be persisted to the EF,they are considered valid objects. Is this correct?

是。

Is the domain model the EF model?

如果您使用EF代码第一种方法，那么是，否则否(如果EF用EF特定属性和类别污染域名)。

There is no business logic in them,they are just used to transport objects between the service(s) and the EF. Is this correct?

是。

I am implementing Interfaces here with generic repository. Then you could extend the generic repository for special needs?

是的，但不要太过分。通常存储库用于CRUD操作。它应该包含业务逻辑的服务。

Is a business object equal to a domain object?

是。

How much logic should a domain object contain?

这将取决于您对您正在工作的特定项目的领域逻辑的数量以及您可能从旧的项目或其他人工作过的任何现有域逻辑。

Dependency Injection – Should I be using this?

是的，一点没错。

I understand how it works,just don’t get the real benefit

它在应用程序的不同层次之间提供较弱的耦合，从而使其更容易在其他项目中进行单元测试和重用。

I think the community would benefit from some sort of wiki that contained all the best practices with code samples.

我同意。

Is there something like that out there?

我对此表示怀疑。

BTW – I think StackOverflow needs a little,“Buy Me A Beer” button next to the “Accept Answer” checkbox

不能同意更多。