tags:

views:

584

answers:

2

I am wondering how to use Model Binding in a scenario where I am returning information from more than one entity on a page?

I want to display a combination of fields from two separate entities, ie Customer + Address. I am using Microsoft's DAAB and custom business entities for my model.

Any ideas?

A: 

You can use ViewData to pass multiple models to a view.

SomeControllerMethod()
{
    ...
    ViewData["Customer"] = myCustomer;
    ViewData["Address"] = myAddress;
}

And the view:

Customer name: <%= (ViewData["Customer"] as Customer).Name %>
Street: <%= (ViewData["Address"] as Address).Street %>
Serhat Özgel
This passes multiple objects to the view, they are not models, you will not be able to access their properties through the views Model object.
Mark Dickinson
+2  A: 

If you are trying to bind to multiple models on postback, you should try using the Bind attribute and specifying the prefixes used for each model in your arguments. In some scenarios -- where you may not be able to use separate prefixes for your model elements -- you might find this easier to do with multiple TryUpdateModel and separate whitelists rather than putting the models in the parameters.

public ActionResult Update( [Bind(Prefix="Customer")]Customer customer,
                            [Bind(Prefix="Address")]Address address )
{
   ...
}

This would assume you have a ViewModel like:

public class CustomerAddressModel
{
    public Customer Customer { get; set; }
    public Address Address { get; set; }
}

and reference it like:

<%= Html.TextBox( "Customer.Name" ) %>
...
<%= Html.TextBox( "Address.Street" ) %>

or, using TryUpdateModel,

public ActionResult Update( int id )
{
    var customer = db.Customers.Where( c => c.ID == id ).Single();

    var whitelist = new string[] { "name", "company", ... };
    if (TryUpdateModel( customer, whitelist ))
    {
        var addressWhitelist = new string[] { "street", "city", ... };
        if (TryUpdateModel( customer.Address, addressWhitelist ))
        {
            ...
        }
    }

}

In this case, your model might contain just the fields from the two different models that you are trying to update.

public class CustomerAddressModel
{
    public string Name { get; set; }
    public string Company { get; set; }
    public string Street { get; set; }
    ...
}
tvanfosson
+ but maybe "try/catch with UpdateModel" is better than this "nested if(TryUpdateModel" construction?
eu-ge-ne
@eu-ge-ne -- maybe. It would depend on how you handle updating the model state on errors. Without actually writing the tests for the code it's hard to tell exactly what should be done.
tvanfosson