Databases
StackOverflow2013
Postsdbo
POCorrect use of Model vs Controller in MVC / ASP.NET MVC
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCorrect use of Model vs Controller in MVC / ASP.NET MVC
    primarykey
    data
    text
    <p>I have a Service class with a method called GetProducts(). That encapsulates business logic and calls the repository to get a list of products.</p> <p>My MVC view wants to show that list of products as an MVC SelectList. Where is the correct place for that logic to go. I seem to have 3 options:</p> <ol> <li><p><strong>Model</strong></p> <p>The Model should expose a property called <code>ProductSelectList</code>. When the getter of this property is called by the View, the Model should call <code>Service.GetProducts()</code> and convert the result to a SelectList before passing it on. </p> <p>Plausible argument: <em>The Model should make calls to business logic and the repository. The View should merely render predetermined data. The Controller should not be involved, save for passing contextual data to the Model.</em></p></li> <li><p><strong>View</strong></p> <p>The View should contain code that calls <code>Service.GetProducts()</code> directly and converts the result to a SelectList inline.</p> <p>Plausible argument: <em>The View should call for this data directly as it is specifically for use on the View. There is no need to involve the Model or Controller, as we are calling an abstracted Service method anyway, so anything else just adds extra overhead.</em></p></li> <li><p><strong>Controller</strong></p> <p>The Controller should make the call to <code>Service.GetProducts()</code>, convert the results to a SelectList and pass it through to the Model, which should contain a simple <code>ProductSelectList</code> property. The View will access this property for rendering.</p> <p>Plausible argument: <em>The Controller knows which parameters to provide to the Service method, so it should make the call. The Model should be a simple placeholder for data, filled by the Controller. The View's job is to simply render the data from the Model.</em></p></li> </ol> <p>I have a <em>feeling</em> that the correct answer is <strong>Model</strong>, but the other two make some reasonable points. Perhaps I've muddied the waters by already having a Service class that's separate to the Model?</p> <p>Would anybody care to share their opinion? Is this just a matter of taste?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJames McCormack
    1. USJames McCormack
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    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. POCorrect use of Model vs Controller in MVC / ASP.NET MVC
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCorrect use of Model vs Controller in MVC / ASP.NET MVC
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCorrect use of Model vs Controller in MVC / ASP.NET MVC
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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