ASP.net MVC部分视图表单需要父模型的属性

Question

I'm trying to structure my controllers and views in such a way that all of my views are strongly typed and I am not using ViewBag. I have a base view model that I inherit from, create one "container" view model per view, plus a view model for each form.

For this example let's focus on a Zone entity that can consist of a group of countries (might be used for calculating shipping, VAT, etc):

public class BaseViewModel
{
    public string Title { get; set; }
    public string MetaDescription { get; set; }
    public string CanonicalUrl { get; set; }
    public Website Website { get; set; } // class that contains properties like site name, base url, use ssl, etc
}

public class ZoneCreateForm
{
    [Key]
    public int Id { get; set; }

    [Required]
    public string Name { get; set; }

    [DataType(DataType.MultiLineText)]
    public string Description { get; set; }

    public int[] CountryIds { get; set; } // Selected country ids
}

public class ZoneCreateViewModel : BaseViewModel
{
    public IEnumerable<Country> Countries { get; set; } // All countries. Used to create a dropdown list to select from

    public ZoneCreateForm CreateForm { get; set; }
}

I was trying to limit my "form models" to only the fields that are posted to the form. This helps scaffolding by eliminating the properties from the base model, and AutoMapper in the controller action on the post.

However, in this example I need access to the Countries property of the parent model in order to create the drop down list of all the countries.

The way I see it, I have some options:

1. Give in and stuff the countries into the ViewBag so they are accessible from the CreateForm partial view.
2. Make the Countries part of the ZoneCreateForm view model and use [Bind(Exclude="Countries")] on the controller action to avoid over-posting
3. Something else I'm not thinking of?

Is there a "standard" way of handling this? Most of the examples I've seen strewn across the web are using the domain models, rather than view-specific models with any inheritance and sub-models. Whenever they have additional data needs they just stuff it into ViewBag, which seems dirty to me.

Answer 1

What version of MVC you are using? With the MVC6 you can add dependency injection in view and not have this in your model.

Example:

• Getting Lookup Data Into You View ASP.net MVC 6 Version
• Dependency injection in ASP.NET 5