Note that there are some explanatory texts on larger screens.

plurals
  1. US1adam12
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. COThats good, you don't need toolkits to do MVVM. There are many ways to share the model between different VM. You might, for example follow a type repository pattern (http://msdn.microsoft.com/en-us/library/ff649690.aspx). Depending on your scenario you you might just new up model objects in your ViewModels. I often create classes services in my application which handle creating and caching of the models (not unlike the repository pattern), which can be requested as required by the ViewModels.
      singulars
    2. COI agree about the codebehind - too many people waste time coming up with elaborate MVVM friendly solutions to problems which are solved easily and more efficiently with a line of code in the codebehind. However I would add equally don't fall into the trap thinking you need to stick religiously to design patterns. No one is buying your app for the theoretical purity of its MVVM implementation. Rather spend your time worrying about your user experience and performance, because that is actually what is going to get people to download your app.
      singulars
    3. COTombstoneHelper only manages the contents of TextBoxes, PasswordBoxes, CheckBoxes, RadioButtons, Sliders, ListBoxes and ScrollViewers by default. It is not working because you are displaying for values to TextBlocks, which are not handled automatically by TombstoneHelper. You could either look into TombstoneHelper's extensiblity model to see how you can add support for TextBlocks otherwise you could display your data in TextBoxes instead.
      singulars
 

Querying!

 
Guidance

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