Home/ Questions/Q 3483080
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T10:37:56+00:00

I am developing a WPF application in which it will reference a class library

  • 0

I am developing a WPF application in which it will reference a class library that contains mostly business objects and some methods to manipulate those objects. Since this library is being used in conjunction with WPF, I have the need to use the INotifyPropertyChanged interface.

However, I do see future uses in the library which may not specifically rely on WPF (or posses the need for property change notifications) as the presentation layer. In your professional experience, would it be better to omit the interface to ensure the DLL is “clean” from unnecessary code for future uses by finding an alternative method, or use the interface and move on?

(obviously, this could be applied to a variety of other programming practices).

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I don’t agree that INotifyPropertyChanged behavior is only to reside within the ViewModel. While INotifyPropertyChanged is heavily used within the Presentation layer, it’s value extends beyond the Presentation layer.

    Every one of my Models generally contains INotifyPropertyChanged behavior, not solely the ViewModel.

    What this boils down to is if you can convince yourself that the INotifyPropertyChanged behavior may be used external to the Presentation layer by a consumer, leave it in.

    • 0