In MVVM should the ViewModel or Model implement INotifyPropertyChanged?

by

I strongly disagree with the concept that the Model should not implement the INotifyPropertyChanged. This interface is not UI specific! It simply informs of a change. Indeed, WPF heavily uses this to identify changes, but that doesn’t mean it is an UI interface.
I would compare it to the following comment: “A tire is a car accessory“. Sure it is, but bikes, buses, etc. also use it. In summary, do not take that interface as an UI thing.

Having said that, it doesn’t necessarily mean I believe that the Model should be providing notifications. In fact, as a rule of thumb, the model should not implement this interface, unless it is necessary. In most cases where no server data is pushed to the client app, the model can be stale. But if listening to financial market data, then I do not see why the model cannot implement the interface. As an example, what if I have non-UI logic such as a service that when it receives a Bid or Ask price for a given value it issues an alert (ex. through an email) or places an order? This could be a possible clean solution.

However, there are different ways of achieving things, but I would always argue in favor of simplicity and avoid redundancy.

What is better? Defining events on a collection or property changes on the view model and propagating it to the model or having the view intrinsically update the model (through the view model)?

The bottom line whenever you see someone claiming that “you can’t do this or that” it is a sign they do not know what they are talking about.

It really depends on your case and in fact MVVM is a framework with lots of issues and I am yet to see a common implementation of MVVM across the board.

I wish I had more time to explain the many flavors of MVVM and some solutions to common problems – mostly provided by other developers, but I guess I will have to do it another time.

More Related Contents:

  1. Implementing INotifyPropertyChanged – does a better way exist?
  2. Data binding to SelectedItem in a WPF Treeview
  3. Binding a WPF ComboBox to a custom list
  4. ICommand MVVM implementation
  5. Notify ObservableCollection when Item changes
  6. ViewModels in MVC / MVVM / Separation of layers- best practices?
  7. WPF: Binding a ContextMenu to an MVVM Command
  8. Why use MVVM? [closed]
  9. What’s the best way to pass event to ViewModel?
  10. What is difference between MVC, MVP & MVVM design pattern in terms of coding c#
  11. How to implement INotifyPropertyChanged in C# 6.0?
  12. MVVM show new window from VM when seperated projects
  13. Entity vs Model vs View Model
  14. Binding ComboBox SelectedItem using MVVM
  15. Disallow/Block selection of disabled combobox item in wpf
  16. Binding SelectedItems of ListView to ViewModel
  17. Mvvm model ViewModel
  18. MVVM Sync Collections
  19. How do you pass a BitmapImage from a background thread to the UI thread in WPF?
  20. One ViewModel for UserControl and Window or separate ViewModels
  21. View Models and dependency injection
  22. The component does not have a resource identified by the uri
  23. ScrollIntoView for WPF DataGrid (MVVM)
  24. How to set focus to textbox using MVVM?
  25. Binding Commands to Events?
  26. How to have multiple pairs “View-ViewModel”?
  27. Accessing a property in one ViewModel from another
  28. Add context menu in datagrid, how to get the select Item value
  29. Limit binding updates per second
  30. Is it wrong to use the Dispatcher within my ViewModel?

Leave a Comment