StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>If the business logic that goes into creating a view model is quite complex I generally extract it into a helper method that I can test independently of the controller. </p> <p>However, that aside, your creation of the view model is perfectly fine within the controller as it is. As has already been noted, how your generating the select list could be made much simpler (not to mention reusable).</p> <p>Here is a ToSelectList extension of IEnumerable along with an example of usage: </p> <pre><code>public static List<SelectListItem> ToSelectList<T>( this IEnumerable<T> enumerable, Func<T, string> value, Func<T, string> text, string defaultOption) { var items = enumerable.Select(f => new SelectListItem() { Text = text(f) , Value = value(f) }).ToList(); if (!string.IsNullOrEmpty(defaultOption)) { items.Insert(0, new SelectListItem() { Text = defaultOption, Value = string.Empty }); } return items; } </code></pre> <p>Within your view model you could add a property like so:</p> <pre><code>IEnumerable<SelectListItem> Employees { get; set; } </code></pre> <p>Within your controller (i'm assuming that your repo is returning IEnumberable):</p> <pre><code>var employees = new IEnumerable<Employee>(); using (var gr = new GenericRepo<Employee>()) { employees = gr.Get(); } vm.Employees = employees.ToSelectList(x=>x.FirstName + " " + x.LastName, x=>x.Id, "-- Select Employee --") </code></pre> <p>And then to setup your drop down list in the view it would look something like:</p> <pre><code>@Html.DropDownListFor(model => model.EmployeeId, Model.employees) </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload