How to build the ViewModel in MVVM not to violate the Single Responsibility Principle?

Question

Robert Martin says: \"There should never be more than one reason for a class to change\".

Let\'s consider the ViewModel class which is bound to a View. It is

Answer 1

I agree with gcores.

Once you see ViewModel grow to more than two screenfuls of text, it is time to consider splitting ViewModel into several child models.

Another rule of thumb is that I never have more than two levels of nesting inside XAML file -- if one part of the view becomes too complex, it is time for view refactoring -- extract inner XAML into separate UserControl and create corresponding ViewModel, which will be default data context on child view.