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 just a quick question about how to properly pass data to a view using the MVC pattern.
I have an EditProfile/Register model (Name, Email, Country). The View has a country dropdown list, and I need to pass it a list of countries.
Is it to correct to create a new model (just for the view), that basically encapsulates my EditProfile/Register model, and a List? Do I create this view specific model in the controller? (as opposed to my data access project).
Thanks!
View models (for ASP.Net MVC views) are not related to domain models (one in data layer) except the name. This MVC: Data Models and View Models question covers the differences/similarities in details.
You create view model somewhere in your ASP.Net MVC project (not in data layer) and usually put in “Models” or “ViewModels” folder sibling to Controllers folder. Depending on views some view model classes can be shared, but you’ll also have some that used by single view.