c# mvc model vs viewbag

Question

Suppose you have a list of People A and a list of People B in a page. And these two are seperate classes in L2S, representing two different tables. Therefore, you cannot pas

Answer 1

I would do it the third way. Additionally, if you are going to render identical html for each person in both arrays, I would concat them before foreach:

var person in Model.PeopleA.Concat(Model.PeopleB)

Answer 2

No, there is not any better idea. In asp.net MVC, M stands for ViewModels, not the Business, Domain models. It is recommended to create ViewModels for your views and it's not reccomended to use Business Models. You should design your ViewModels to fit the need of controller interactions with Domain, and from controller to view interactions

Answer 3

I usually create a Model for the page, and name it as such, eg AccountDetailsPageModel. Then other models can be properies of this for complex pages.

Answer 4

Your first and third options seem both OK.

ad 1) "only using them once" is not a good argument-against. Use Partial views to organize views.

ad 2) Use the Viewbag to add small items like a lookup list.

ad 3) ViewModels are (becoming) common in MVC. This is probably the best approach.

Answer 5

Creating a ViewModel specific to the page, as your option 3 is the way I would do it.

I believe this is also the recommended approach.