So far I’ve focused on how viewmodels define what a UI element looks like through property setting. But any viewmodel worth its salt generally also does stuff. And that’s where

Because view models serve as the glue between a particular UI element and the data layer they don’t inherently have any “awareness” of each other. That’s fine when changes to

Building viewmodels using the Microsoft MVVM toolkit is straightforward. It’s descended from the old MVVM-Light library so if you’ve used that the transition is pretty simple. The main elements of

Designing a UI is persnickety. You want it to look just right. But what it looks like is often a function of the data it’s displaying. For example, the height

I’ve recently been playing around with the composition root concept as the “next step” beyond dependency injection1. The basic idea is you register, via dependency injection, all the objects in

With WPF now being supported under Net5 and Visual Studio 2019 I thought it was time to re-acquaint myself with it. Since I learn mostly by doing I figured I’d