Timeline for When using MVVM, is it okay to use property injection on a view model in WPF?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 2, 2018 at 12:10 | history | edited | Snoop |
edited tags
|
|
| Dec 9, 2016 at 15:29 | vote | accept | Snoop | ||
| Dec 8, 2016 at 15:31 | answer | added | Rachel | timeline score: 2 | |
| Dec 5, 2016 at 16:49 | comment | added | Snoop | As always, thank you @RobertHarvey. I guess that statement isn't very clear, the view-model only obtains data from my model... Furthermore, this data is bound by the view via public properties. | |
| Dec 5, 2016 at 16:13 | comment | added | Robert Harvey |
The view-model will then utilize those objects to do whatever the application is supposed to do -- If that means doing anything other than UI interaction logic, it probably is not kosher. Business logic belongs in the Model, not the ViewModel..
|
|
| Dec 5, 2016 at 16:09 | comment | added | Robert Harvey | I would start with this CodeProject article. This one also looks promising. Once you have a good grasp of MVVM in a WPF context, it should become apparent whether or not what you're trying to do is kosher. | |
| Dec 5, 2016 at 12:18 | history | edited | Snoop | CC BY-SA 3.0 |
edited title
|
| Dec 5, 2016 at 11:54 | history | asked | Snoop | CC BY-SA 3.0 |