blocks|key|1127052|text|这可能并不合适，但是如果您只是将验证规则/注释从您的模型移动到您的ViewModels中呢？在我参与的几个项目中，我们选择了阻止视图访问通过其对应的ViewModel公开的信息以外的任何内容。由于所有数据交互都将通过ViewModel执行，因此不需要对模型对象进行验证。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1127053|这个论点的反面是，您可以很容易地复制某些验证规则，因为不同的ViewModels可能与相同的模型接口。在这种情况下，简单地将模型声明为在ViewModel上公开的属性可能是有意义的。对于回发，它们可以接受模型作为其参数，从而允许ModelBinder基础结构处理请求。在这种情况下，如果ModelState.IsValid为false，则只需在重新显示视图之前将属性重新分配给ViewModel即可。|1127054|我建议您将注释移动到您的ViewModels。这是有意义的，因为许多视图是a)几个模型组合的结果，或者b)模型数据的子集。|1127055|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

This may not be appropriate, but what if you just moved your validation rules/annotations from your Models to your ViewModels? In a few of the projects I've been on, we've chosen to prevent the View from accessing anything but information exposed through its corresponding ViewModel. Since all data interaction would be performed through the ViewModel, there wouldn't be a need to have validation on your Model objects.

The counter to this argument is that you could easily duplicate certain validation rules, since different ViewModels might be interfacing with the same Models. In this case, it might make sense to simply declare your Model as a property exposed on your ViewModel. For postbacks, they could accept a Model as their parameter, allowing the ModelBinder infrastructure to handle the request. In this case, if ModelState.IsValid is false, you could just reassign the property to your ViewModel before redisplaying the View.

I would recommend moving your annotations to your ViewModels. It makes sense since a lot of Views are a) the result of composition of several models or b) a subset of model data.

blocks|key|1342235|text|也许我们根本不应该使用视图模型？并在模型层实体上定义验证规则。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1342236|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Probably we shouldn't use view models at all?
And define validation rules on model layer entities..

blocks|key|1127153|text|DataAnnotation属性用于验证输入并向最终用户提供UI反馈。这实际上是它们唯一的预期用途。我对UI对象和业务对象使用不同的验证策略，因此DA验证属性最终只显示在向用户显示的模型上。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1127154|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The DataAnnotation attributes are about validating input and giving UI feedback to the end user. That's really their only intended use. I use different validation strategies for UI objects and business objects, so the DA validation attributes only end up on models being shown to the user.

blocks|key|1127244|text|我也考虑了一段时间了。我完全理解布拉德的回答。但是，让我们假设我想使用另一个验证框架，该框架既适用于注释域实体，也适用于注解视图模型。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1127245|在纸面上，我能想到的唯一仍然使用属性的解决方案是创建另一个属性，该属性“指向”您在视图模型中镜像的域实体的属性。下面是一个例子：|1127246|//+In+UI+as+a+view+model.
public+class+UserRegistration+{
++[ValidationDependency<Person>(x+=>+x.FirstName)]
++public+string+FirstName+{+get;+set;+}

++[ValidationDependency<Person>(x+=>+x.LastName)]
++public+string+LastName+{+get;+set;+}

++[ValidationDependency<Membership>(x+=>+x.Username)]
++public+string+Username+{+get;+set;+}

++[ValidationDependency<Membership>(x+=>+x.Password)]
++public+string+Password+{+get;+set;+}
}|code-block|syntax|javascript|1127247|可以扩展像xVal这样的框架来处理这个新属性，并在依赖类的属性上运行验证属性，但是要使用视图模型的属性值。我只是没有时间来更多地充实这一点。|1127248|有什么想法吗？|1127249|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I've been considering this as well for a while now. I totally understand Brad's reply. However, let's assume I want to use another validation framework that is suitable for annotating both domain entities and view models.

The only solution I can come up with on paper that still works with attributes would be to create another attribute that "points" to a domain entity's property that you are mirroring in your view model. Here's an example:

<pre><code>// In UI as a view model.
public class UserRegistration {
 [ValidationDependency&lt;Person&gt;(x =&gt; x.FirstName)]
 public string FirstName { get; set; }

 [ValidationDependency&lt;Person&gt;(x =&gt; x.LastName)]
 public string LastName { get; set; }

 [ValidationDependency&lt;Membership&gt;(x =&gt; x.Username)]
 public string Username { get; set; }

 [ValidationDependency&lt;Membership&gt;(x =&gt; x.Password)]
 public string Password { get; set; }
}
</code></pre>

A framework like xVal could possibly be extended to handle this new attribute and run the validation attributes on the dependency class' property, but with your view model's property value. I just haven't had time to flesh this out more.

Any thoughts?

blocks|key|1342441|text|事实证明，AutoMapper可能能够自动为我们做这件事，这是最好的情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1342442|AutoMapper-用户:将验证属性传输到视图模型？|1342443|http://groups.google.com/group/automapper-users/browse_thread/thread/efa1d551e498311c/db4e7f6c93a77302?lnk=gst&q=validation#db4e7f6c93a77302|offset|length|1342444|我还没有抽出时间尝试那里提出的解决方案，但打算很快就会。|1342445|(Cross也在我的(dupe)问题上发布了这一点)。|1342446|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|3W|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@$F|V|G|W|1|X]]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Z|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|E]]]]

It turns out that AutoMapper may be able to do this for us automagically, which is the best case scenario.

AutoMapper-users: Transfer validation attributes to the viewmodel? 
<a href="http://groups.google.com/group/automapper-users/browse_thread/thread/efa1d551e498311c/db4e7f6c93a77302?lnk=gst&amp;q=validation#db4e7f6c93a77302" rel="nofollow noreferrer">http://groups.google.com/group/automapper-users/browse_thread/thread/efa1d551e498311c/db4e7f6c93a77302?lnk=gst&amp;q=validation#db4e7f6c93a77302</a>

I haven't got around to trying out the proposed solutions there, but intend to shortly.

(Cross posted this on my (dupe) question as well).

Here is the lay of the land. Like most people I have my domain object and I have my view models. I love the idea of using view models, as it allows for models to be created specifically for a given view context, without needing to alter my business objects.

The problem I have is with type level validation defined on my domain object and getting those rules to the client. In this case lets say I am using data annotations to describe the validation rules, when I move the data from the domain object to the view model, the view model no longer knows what validation it should get the interface to perform (because the validation is defined back on the domain object).

With MVC 2 you can get it to automatically perform client/server side validation, based on the validation rules of the current object. But because the validation rules are defined on the domain object and not the view model, I would have to duplicate the validation rules on the view model to get this to work.

How do others deal with this type of issue? My thinking is that besides mapping the data from the domain object to the view model, we also need to map across the validation rules, but I haven't really seen others talking about this issue... Brad Wilson has recently talked about this issue at length but hasn't really addressed the duplication of rules on the domain object and on the view models... what are your thoughts?

Cheers
Anthony

Does ASP.Net MVC 2 validation need some more thought in terms of patterns and use?

服务器

这是这片土地的基本情况。像大多数人一样，我有自己的域对象和视图模型。我喜欢使用视图模型的想法，因为它允许专门为给定的视图上下文创建模型，而不需要更改我的业务对象。我遇到的问题是在我的域对象上定义的类型级别验证，并将这些规则发送到客户端。在这种情况下，假设我使用数据注释来描述验证规则，当我将数据从域对象移动到视图模型时，...

问ASP.Net MVC2验证是否需要在模式和使用方面进行更多考虑？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.Net MVC2验证是否需要在模式和使用方面进行更多考虑？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.Net MVC2验证是否需要在模式和使用方面进行更多考虑？
EN