is passing Viewbag a best approach in asp.net-mvc 3

Question

We've a lots of controllers which return JSON result to the View. The view needs to be dynamic based on user's contract type and user's home location.

I'm thinking of passing contract type and other properties using MVC 3.0 ViewBag object. View then access this object and toggle the UI.

Could some one help me if this is the best approach? The draw back of this approach is that every controller needs to pass viewbag to the UI or is it good to store the required object in session and access it from View.

Thanks.

check this http://stackoverflow.com/a/10443526/1182982 – Yasser Shaikh Sep 10 '12 at 11:17 — Yasser Shaikh, Sep 10 '12 at 11:17

score 3 · Answer 1 · edited May 23 '17 at 12:03

3

ViewBagand ViewData are more of a worst approach. The ViewModel should contain everything the View needs.

If you want to know more about the why and how, have a look at this excellent explanation by Darin Dimitrov: ViewBag, ViewData and TempData

Update: In the comments you write that you can't use a ViewModel because you're retuning a JSON result. Passing JSON can be done with a ViewModel as well:

public JsonResult SomeAction()
{
    SomeViewModel model = ...;
    return Json(model, JsonRequestBehavior.AllowGet);
}

edited May 23 '17 at 12:03

Community

1
1

answered Sep 10 '12 at 08:32

Dennis Traub

50,557
7
93
108

Can't use viewmodel as we are passing json result back to view. – Nil Pun Sep 10 '12 at 08:54
@Myagdi I have updated my answer and added an example for `JsonResult` – Dennis Traub Sep 10 '12 at 09:01

is passing Viewbag a best approach in asp.net-mvc 3

1 Answers1