Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have multiple MVC 3 forms that need form validation on certain fields (mostly to test empty submission). Some of my view models come directly from an ORM classes, so I don’t have access to attribute required fields. Do I need to create additional classes (i.e., make a mega-ViewModel above the ORM class) to populate so I can attribute these or do other options exist (such as jQuery)?
So those are not real view models but models. I would recommend you defining specific view models for each view/form. The view model should contain only the properties used by the view and be decorated with the necessary validation attributes for this particular view. This way you can handle validation as you like. So my advice is to always create and use view models which are specifically tailored to the requirements of a given view and map them to and from the domain models.
You may take a look at the following answer for some ideas.