Home/ Questions/Q 3693398
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T04:22:22+00:00

There are two common command implementations I’ve seen by Microsoft. One, given by Josh

  • 0

There are two common command implementations I’ve seen by Microsoft. One, given by Josh Smith here,
places commands onto viewmodel classes. Another, given by Robert McCarter here, makes commands accessible via a static class (so we can data-bind to them with x:Static). McCarter’s approach relies more on the use of singletons and static calls than I want to take chances with, so currently I’ve chosen to use Josh Smith’s approach. However, my “main” viewmodel has blown up in size with at least 30 commands now, as I have a Ribbon control in the main window. Is this a sign of bad design i.e. a lack of separation of concerns? or is this common for MVVM apps? It just seems like a lot of responsibility for a single viewmodel.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I don’t think it really matters if you have many commands in the same ViewModel. Commands are just boilerplate code, they don’t really implement anything. If the actual implementation of these commands is in the same ViewModel, however, it could be an issue. You should probably try to break down your class into several components to apply the single responsibility principle.

    • 0