Home/ Questions/Q 8258597
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T02:35:48+00:00

I have a WPF application that should be compact, with minimal possible memory footprint.

  • 0

I have a WPF application that should be compact, with minimal possible memory footprint. The GUI is simple from the point of view of flow, few pages and grids, but quite rich from the point of view of graphics, animations etc.

I have experience writing applications with Prism and I like it very much. But it looks too heavy for simple tasks. It is not a LOB application, but I still need testability, GUI/flow/business separation etc.

Should I use MVVM anyway?

I am not sure if the overhead of using the MVVM design pattern is something I should worry about or not when trying to minimize the memory usage of my application.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Yes, use MVVM if you’re working with WPF

    WPF is designed so you have a UI layer and a data layer, and this suits the MVVM design pattern perfectly. I find it makes the coding and maintenance much faster and easier.

    You don’t have to use a full fledged MVVM framework, or even any MVVM framework at all. You can pick and choose the parts you’re interested in using (a base object that inherits INotifyPropertyChanged, a RelayCommand or DelegateCommand, the messaging system, etc) and drop all the rest. Or you can build your own.

    The amount of overhead is minimal and definitely not worth avoiding the pattern for, however some MVVM frameworks do include unneeded features and can cause some overhead, so be sure you only pick the pieces you want out of them.

    The point is, use the MVVM design pattern if you’re working with WPF. It will make your life, and any future developers that work on the project lives, much easier 🙂

    • 0