不知道如何处理根据 MVC 中的视图而变化的验证
好吧，我对如何处理这个问题有点茫然，我正在寻找关于这个方向的想法。
我正在开发一个带有 Razor 的 ASP.Net MVC 3 网站，该网站将处理一组学校的注册。在注册过程开始时，系统会询问用户他们正在注册哪所学校。他们注册的学校将决定需要哪些信息（一所学校需要 SSN，而另一所学校不需要，一所学校需要驾照，而另一所学校不需要，等等）。我正在使用 LINQ to SQL 并使用 LINQ to SQL 生成的模型作为我的视图模型。我在网站的其余部分中通过属性使用了不引人注目的验证，因此如果可能的话，我想继续这样做。那么如何根据模特所就读的学校来确定模特的属性呢？
我能想到的解决这个问题的一种途径是为每所学校提供一个视图（或一系列视图），并以某种方式使验证取决于正在使用的视图，但我不知道该怎么做通过不引人注目的验证。
或者也许对所有学校使用相同的视图，但有一个自定义验证器
Ok, I'm at a bit of a loss on how to handle this and I'm looking for ideas on what direction to head with this.
I am developing an ASP.Net MVC 3 w/ Razor site that will handle registration for a group of schools. At the beginning of the registration process the user is asked which school they are registering for. What school they're registering for will determine what information is required (one school requires SSN while another doesn't, one requires a driver's license # while another doesn't, etc). I'm using LINQ to SQL and am using the Models generated by LINQ to SQL as my view models. I've used unobtrusive validation through attributes throughout the rest of the site so I would like to continue to do so if possible. So how do I make a model's property required depending on the school they're going to?
One route of solving this that I can think of is to have a view (or a series of views) for each school and, some how, make the validation depend on which view is being used, but I'm not sure how to do that with unobtrusive validation.
Or maybe use the same view for all schools but have a custom validator <RequiredForSchools(requiredSchoolIDs as Integer())> if i could figure out a way to get the SchoolID to the custom validator (both the javascript side of it and the server side).
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
有多少个变量？你能把它压缩到几个，或者少于10个吗？在这种情况下，您可以为每个视图模型使用视图模型，其中具有少量变体可能是最简单的。您根据学校选择视图模型。
如果变化太多，那么您可能必须编写自己的验证属性来做出决定。
how many variables are there? can you condense it down to a few, or less than 10? In that case, you can use view models for each, which with a small number of variations may be the easiest. You choose your viewmodel based on school.
If there are too many variations, then you will probably have to write your own validation attributes that do the deciding.