o_19mgorv9t13a3ko71fev19l81mqa.pdf

@model SportsStore.Domain.Entities.Product
@{
}
ViewBag.Title = "Admin: Edit " + @Model.Name;
Layout = "∼/Views/Shared/_AdminLayout.cshtml";
Edit @Model.Name
@using (Html.BeginForm()) {
@Html.HiddenFor(m => m.ProductID)
@foreach (var property in ViewData.ModelMetadata.Properties) {
if (property.PropertyName != "ProductID") {
@(property.DisplayName ??
property.PropertyName)
@if (property.PropertyName == "Description") {
@Html.TextArea(property.PropertyName, null,
new { @class = "form-control", rows = 5 })
} else {
@Html.TextBox(property.PropertyName, null,
new { @class = "form-control" })
}
}
}
new {
}
@Html.ActionLink("Cancel and return to List", "Index", null,
})
@class = "btn btn-default"
This is a variation on the metadata technique that I used in Chapter 9 and it is something that I find myself using often, even
though I could achieve similar results through the HTML helper methods with the customization techniques I describe in Chapter
22. There is something pleasing about this approach that gels with my development style but, as ever with the MVC Framework,
there are different approaches you can use if processing metadata doesn’t do it for you. You can see how this view is displayed in
the browser in Figure 11-7.
285