Evgeny

This is the second part of Organizing view models in ASP.NET MVC (see Part 1).

So, designing classes for your view models inevitably brings up some new concerns, like how should the Layout view models be implemented (master pages in terms of WebForms view engine).

From my experience, you should create an abstract class like SharedLayoutViewModel with all of the data properties required by your _Lauout.cshtml. Then, make all of the view models of views that use this layout inherit this class. You can use MVC Result filters to fill this model with data in a single place of your app, or, like I do, override the OnResultExecuting method in the common base class for your controllers, and fill it there.

To make your view models easy to find, organize them in a similar fashion as you do for views. I prefer putting all the view models in a single namespace (though in different project directories) and having full name as its class name like ProductsCreateViewModel (if you’re using ReSharper, set NamespaceProvider = False). This way I avoid need of explicit namespace reference in views and controllers. So my final layout looks like this:

In the next part I’ll give a sample of a simple form implemented using the described approach.

Razor is a brand new view engine for MVC. I’ll describe a method to use strongly-typed helpers like TextBoxFor(m=>m.FirstName) in its reusable @helper blocks
If you never heard about it, then read on ScottGu blog.

Suppose you have a checkout model that has two addresses – billing and shipping:

public class CheckoutInfoForm
{
    public CheckoutAddressForm BillingAddress { get; set; }
 
    public CheckoutAddressForm ShippingAddress { get; set; }
}

While each address has model like this:

public class CheckoutAddressForm
{
    public string FirstName { get; set; }
 
    public string LastName { get; set; }
 
    public string Address1 { get; set; }
 
    // and so on
}

How would you generate address fields for both and reuse the markup?
More >