Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • not really an answer but I was wondering the same thing. Also if you look at WPF classes for UI elements etc, they are much bigger than any classes I have developed so far. I also wonder where would you place all you main application code if not in view model? At some point there should be some final class where everything is called from isn't it? Commented May 11, 2022 at 9:24
  • 1
    The ViewModels (a.k.a. presentation models) in MVVM are entirely within the presentation layer. They are meant to be models (representations) of some view (which itself may be a subview). You can in principle apply the same general design guidelines to them, but it will look a little different because ViewModels are usually meant to be used with some kind of a data-binding mechanism between them and the view. However, you might be constrained in some ways design-wise by the MVVM library/framework you're using, so practice might differ from theory. Commented May 11, 2022 at 18:06