Databases
StackOverflow2013
Postsdbo
POASP.NET MVC Where to keep the values for SelectLists
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POASP.NET MVC Where to keep the values for SelectLists
    primarykey
    data
    text
    <p>I've currently got all of this mess at the top of my ViewModels which I feel violates the purpose of a DTO. For example, this is in the constructor of one of my view models -</p> <pre><code> Dictionary&lt;int, string&gt; chargeGroups = new Dictionary&lt;int, string&gt;(); chargeGroups.Add(1, "Administration"); chargeGroups.Add(2, "Annual Leave"); chargeGroups.Add(3, "Bereavement"); chargeGroups.Add(4, "Customer Installation, Setup &amp; Training"); chargeGroups.Add(5, "Customer Support"); chargeGroups.Add(6, "Internal Training &amp; Education"); chargeGroups.Add(7, "Sales &amp; Marketing"); chargeGroups.Add(8, "Sick"); chargeGroups.Add(9, "Software Devel / Maint / Test"); chargeGroups.Add(10, "Software Upgrade / Patch"); chargeGroups.Add(11, "Other"); chargeGroups.Add(12, "Other Absence"); chargeGroups.Add(13, "Warranty"); chargeGroups.Add(14, "Public Holiday"); chargeGroups.Add(15, "Other Paid Leave"); ChargeGroups = new SelectList(chargeGroups, "Key", "Value"); </code></pre> <p>My viewmodel:</p> <pre><code> [DisplayName("Charge group")] public short? ChargeGroup { get; set; } public SelectList ChargeGroups; </code></pre> <p>then in my view:</p> <pre><code> &lt;div class="editor-label"&gt; @Html.LabelFor(model =&gt; model.ChargeGroup) &lt;/div&gt; &lt;div class="editor-field"&gt; @Html.DropDownListFor(model =&gt; model.ChargeGroup, Model.ChargeGroups) @Html.ValidationMessageFor(model =&gt; model.ChargeGroup) &lt;/div&gt; </code></pre> <p>Where should I be putting this stuff?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USNoPyGod
    1. USNoPyGod
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POASP.NET MVC Where to keep the values for SelectLists
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POASP.NET MVC Where to keep the values for SelectLists
      1. USRobert Harvey
      1. VTFavorite
    3. VO
      singulars
      1. POASP.NET MVC Where to keep the values for SelectLists
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWell since this is a ViewModel and not a Model I don't see an issue here. This has to do with rendering a view so it makes sense to be in a ViewModel. On postback I would transform this into a Model before sending to the database so you are not violating the DTO... Anyways, I am interested in other people's opinions on this.
      singulars
      1. POASP.NET MVC Where to keep the values for SelectLists
      1. USJohn Kalberer
    2. COI agree with @JohnKalberer. A ViewModel doesn't have to be a completely anemic DTO, it can contain logic relevant to the View. I would have logic in (or used by) the controller to transform incoming ViewModel data to the Model business layer, and back to outgoing ViewModel data. (One side note: Why is there a `SelectList` on the business model? Isn't `SelectList` specifically an MVC UI element? Business models shouldn't be tightly coupled with a UI implementation.)
      singulars
      1. POASP.NET MVC Where to keep the values for SelectLists
      1. USDavid
    3. COI meant to say ViewModel not model sorry. [post edited]
      singulars
      1. POASP.NET MVC Where to keep the values for SelectLists
      1. USNoPyGod
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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