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 on my controller a Create and an Edit action.
I have for each action a viewmodel. Both viewmodels have approximately 15 properties. 10 are common for both models and the rest differs.
My question : Should I create some base model with the common properties (keeping DRY) or should I dont care here ?
This is almost certainly going to come down to the actual situation you are in. The most important question to ask yourself is: do these shared properties form some kind of base entity? If the answer is yes, you are probably safe having a base class. If not, I would stay away from it and just put the properties on the individual models.
If you are leaving out some properties in the create view model that become editable in the edit view, the shared properties probably do not make up some type of base class, and you should avoid the base view model approach. If the extra properties are just helper properties, like select lists, then you can safely have a base model that has the common properties.