Timeline for MVVM Reporting App Approach ? Data Access Layer?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 6, 2019 at 17:07 | comment | added | whytheq | @MatthewFlynn check out this article msdn.microsoft.com/en-us/magazine/dd419663.aspx the ViewModel talks to the Repository. | |
| Jun 14, 2012 at 15:45 | comment | added | Matthew Flynn | @Rachel--you really do have this backwards--the Model is NOT "dumb objects"--it is the model of your business domain, which can very well have logic and will probably be persistent in some manner. Now you probably want to segregate the means of persistence using DAOs or something, but that would be underneath the Model. The purpose of the ModelView is simply to map/bind the View (UI) to the model. The ModelView should not even care about persistence. | |
| Jan 25, 2012 at 13:09 | comment | added | Rachel | The ViewModel is usually the one to interact with the DAL. Sometimes the DAL is hidden behind another layer, the Repository layer, which is usually the "black box" that does all the data access calls. I've used both methods before (calling the DAL directly from my VM, or working with a Repository object from my VM), and which one I use is usually based on my project's size. | |
| Jan 25, 2012 at 8:33 | comment | added | stuartmclark | @Rachel should I have a data access layer then that either the Model/ViewModel interacts with. I can see where you are coming from with the "dumb" comment and it makes sense. I am unsure of who interacts with the Data access layer then? | |
| Jan 24, 2012 at 19:53 | comment | added | Rachel | Nooooooo don't do that! Models are dumb objects meant for holding data, they should not perform any kind of Data Access! | |
| Jan 18, 2012 at 18:21 | vote | accept | Bat Masterson | ||
| Sep 30, 2017 at 9:50 | |||||
| Jan 16, 2012 at 11:12 | history | answered | stuartmclark | CC BY-SA 3.0 |