Databases
StackOverflow2013
Postsdbo
POFetching data within an ASP.NET MVC ViewModel class?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POFetching data within an ASP.NET MVC ViewModel class?
    primarykey
    data
    text
    <p>For those that create ViewModels (for use by typed views) in ASP.NET MVC, do you prefer to fetch the data from a service/repository from within the ViewModel, or the controller classes?</p> <p>For example, we started by having ViewModels essentially being DTOs and allowing our Controllers to fetch the data (grossly oversimplified example assumes that the user can only change employee name):</p> <pre><code>public class EmployeeViewModel { public String Name; //posted back public int Num; //posted back public IEnumerable&lt;Dependent&gt; Dependents; //static public IEnumerable&lt;Spouse&gt; Spouses; //static } public class EmployeeController() { ... public ActionResult Employee(int empNum) { Models.EmployeeViewModel model = new Models.EmployeeViewModel(); model.Name = _empSvc.FetchEmployee(empNum).Name; model.Num = empNum; model.Dependents = _peopleSvc.FetchDependentsForView(empNum); model.Spouses = _peopleSvc.FetchDependentsForView(empNum); return View(model); } [AcceptVerbs(HttpVerbs.Post)] public ActionResult Employee(Models.EmployeeViewModel model) { if (!_empSvc.ValidateAndSaveName(model.Num, model.Name)) { model.Dependents = _peopleSvc.FetchDependentsForView(model.Num); model.Spouses = _peopleSvc.FetchDependentsForView(model.Num); return View(model); } this.RedirectToAction(c =&gt; c.Index()); } } </code></pre> <p>This all seemed fine until we started creating large views (40+ fields) with many drop downs and such. Since the screens would have a GET and POST action (with POST returning a view if there was a validation error), we'd be duplicating code and making ViewModels larger than they probably should be. </p> <p>I'm thinking the alternative would be to Fetch the data via the Service within the ViewModel. My concern is that we'd then have some data populated from the ViewModel and some from the Controller (e.g. in the example above, Name would be populated from the Controller since it is a posted value, while Dependents and Spouses would be populated via some type of GetStaticData() function in the ViewModel).</p> <p>Thoughts?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UStereško
    1. USBeep beep
    plurals
    1. 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. POFetching data within an ASP.NET MVC ViewModel class?
      1. USBeep beep
      1. VTFavorite
    2. VO
      singulars
      1. POFetching data within an ASP.NET MVC ViewModel class?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POFetching data within an ASP.NET MVC ViewModel class?
      1. USAASoft
      1. VTFavorite
    1. COIEnumerable<Spouse>? What's with the polygamist pattern? :-D
      singulars
      1. POFetching data within an ASP.NET MVC ViewModel class?
      1. USDaniel Liuzzi
 

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