In my opinion, you should never use ViewBag without a very, very good reason. Brad Thomas’ answer points out a rare example of one of those good reasons. Say you have a master layout (or a partial view) shared by an entire website and dozens of strongly-typed Views that each have their own Model. How … Read more
For anyone who is trying to do it without modifying your ViewModels AND not loading all your records from the database. Repository public List<Order> GetOrderPage(int page, int itemsPerPage, out int totalCount) { List<Order> orders = new List<Order>(); using (DatabaseContext db = new DatabaseContext()) { orders = (from o in db.Orders orderby o.Date descending //use orderby, … Read more
tl;dr Is it acceptable for a ViewModel to contain instances of domain models? Basically not because you are literally mixing two layers and tying them together. I must admit, I see it happen a lot and it depends a bit on the quick-win-level of your project, but we can state that it’s not conform the … Read more
I create what I call a “ViewModel” for each view. I put them in a folder called ViewModels in my MVC Web project. I name them after the controller and action (or view) they represent. So if I need to pass data to the SignUp view on the Membership controller I create a MembershipSignUpViewModel.cs class … Read more