MVVM consists of three important parts—Model, View, and the ViewModel. The Model represents the data; the View is the actual UI, which displays the relevant parts of the model; and the ViewModel is the mechanism that hands out the required data to the view. A ViewModel basically exposes properties and commands, and maintains the relevant state of the view.
If we compare the MVVM pattern with a bike (as represented in the following screenshot), the bike Body is the View, the Fuel is the Model and the Engine of the bike is the ViewModel, which moves the View (bike body) by burning/using the Model (Fuel):
In our application, we used the DataContext to define the binding between the View and the ViewModel, which we then used to access the properties. If you now navigate to the MainWindow.xaml.cs file, you won't see any additional code except the constructor of the code-behind class.
In the MVVM pattern, our intention is to keep the code-behind file (MainWindow...