InterviewSolution
Saved Bookmarks
InterviewSolution
| 1. |
Does Each And Every Piece Of Child Content That You Separate Into Its Own Xaml File Necessarily Needs To Be An Mvvm View? |
|
Answer» No, if the chunk of content just PROVIDES the structure to render something to the screen and does not support any input or manipulation by the user for that content. It may not need a SEPARATE ViewModel, but it COULD just be a chunk XAML that renders BASED on properties exposed by the parents ViewModel. No, if the chunk of content just provides the structure to render something to the screen and does not support any input or manipulation by the user for that content. It may not need a separate ViewModel, but it could just be a chunk XAML that renders based on properties exposed by the parents ViewModel. |
|