Home/ Questions/Q 6388625
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T03:18:09+00:00

In WPF, I have a property with only a get{}. The value is coming

  • 0

In WPF, I have a property with only a get{}. The value is coming from the return of method. NotifyPropertyChanged is often used within a property set{}. It can then notify the UI and the updated value is displayed. But with a get{} only, there isn’t a way of detecting if a new or different value is available since you have to execute the method to check.

Is there some way to update the UI without having to keep a local value that contains the last value from the method, in which case a compare would need to be done?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    But with a get{} only, there isn’t a way of detecting if a new or different value is available since you have to execute the method to check.

    The problem boils down to this: What is changing the property? The method that changes the property should call your NotifyPropertyChanged with the name of the property, which will, in turn, cause WPF to refetch the value and update the user interface.

    WPF doesn’t care where the PropertyChanged event gets raised – it just listens for it, and refreshes the binding as needed.

    Edit in response to comment:

    It sounds like this may be the result of performing some operation upon your Model class. In this case, it’s common that you know that one or more properties may change, but not necessarily which ones. If your Model implements INotifyPropertyChanged, you can subscribe to that and “bubble up” the notifications to the UI via your NotifyPropertyChanged method. If it does not, however, there is another option.

    If you know that one or more properties may change, you can raise a PropertyChanged event with string.Empty as the PropertyName in the EventArgs. This will cause all bound properties to get refreshed by WPF. This is likely just a matter of putting something like this in your code:

    this.Model.DoSomething(); // This will change 1+ properties
this.NotifyPropertyChanged(string.Empty); // Refresh our entire UI

    I wouldn’t recommend doing this everywhere, however, as it does add overhead – but it’s often the cleanest solution if you don’t know which properties will change when you perform an operation.

    • 0