Browse by Tags

Tagged Content List
  • Blog Post: Reusing ViewModels in a Universal App – Part 5

    Wow, its been quite the journey but here we are finally at the end. To restate the previous articles – We took a Windows store app that was coded without a ViewModel . We refactored the code to have a ViewModel which is placed in a shared location, along with the Model. The final View has almost...
  • Blog Post: Reusing ViewModels in a Universal App – Part 4

    To restate where part 3 ended – We have migrated all the buttons and TextBox to use the ViewModel . What is left is the display of the items on the stack and the mode radio buttons. Handling Radio Buttons There are a few different ViewModel patterns which work with RadioButtons . Option...
  • Blog Post: Reusing ViewModels in a Universal App – Part 3

    To restate where part 2 ended – We took the MyCalc app and created an empty ViewModel class. We then implemented DelegateCommand so we could expose ICommand objects from the ViewModel . We used that to create commands for the majority of the buttons and modified the XAML to use them. This allowed...
  • Blog Post: Reusing ViewModels in a Universal App – Part 2

    To restate where part 1 ended - We have our Windows App, MyCalc , which currently has no ViewModel and instead has all the logic in the View layer. Which means it can’t be reused for different views, such as one for phone. Our goal is to move that logic into a shared ViewModel and add a Phone view...
  • Blog Post: Reusing ViewModels in a Universal App – Part 1

    There is an increasing trend for Microsoft platforms to build what is called a “Universal App”. In its ideal it is an application that you code once, and then it runs on desktop, tablet and phone platforms. This opportunity introduces new challenges – with a main one being that the...
  • Blog Post: Mouse vs Keyboard and ContextMenus

    Recently I was asked to modify one of my controls so the user of the control could get the proper placement of thier context menus. My intial response was for them to use the placement properties on the ContextMenu/ContextMenuService to achieve the right positioning. Then the real issue came out....
  • Blog Post: Creating Adorner content in XAML

    I've been working on a problem of having a "popup" control in my project. For various reasons the Popup class isn't working for this scenario, because the scenario is outside the designed scope of Popup. So I've been looking at the AdornerLayer as a way to get a popup effect. One of the things I noticed...
Page 1 of 1 (7 items)