In this post I’ll create the simplest application that covers the basics of MVVM in the context of unit testing. The application does just click counting - it’s the simplest app that I could think of that can be used to demonstrate view models,
INotifyPropertyChanged, data binding, commands and unit testing. We will NOT be using any MVVM frameworks.
Often, when you’re working you want to quickly open a file, edit that and run it so you can test it. What happens when you press
F5in Visual Studio is that it will start some other project (when you have a solution with more than 1 project). In this post you’ll learn a simple trick that allows you to start the project where the file you just edited is.
Normally you want to make animations using storyboards and then some code behind to start the animations. In this post I’ll show you a way to implement the animation in a very clean and MVVM way on a very simple application.
In a previous post about attached properties, we saw how we can change the background of an UI element by attaching an external property to that element. In this post, we’re going to do the same, but this time using the evolved version: Blend Behaviors.
In this post we’re going to see how to dynamically get the value of a property by using only its name. This started from me trying to understand how data binding works in XAML and implementing it myself. For this, I needed a view model which implements the
INotifyPropertyChangedand then subscribe to its