INotifyPropertyChanged in .NET 4.5

Implementing INotifyPropertyChanged in your XAML-based application has always been a point of hot debate. To date there are a variety of techniques – from the original (and fastest) “magic” string indicating the property name to the much slower, but compiler-checked Lambda expression tree implementation which provides refactoring safety. Both styles are included in my MVVM library ( Trying to keep the performance of a raw string-based approach, but get the compile-time safety of the expression tree approach has been the goal of many WPF and Silverlight devs for the past few years. We’re getting closer…

.NET 4.5 (included in VS11 beta this week) brings a new option to the table in the form of the new [CallerMemberName] attribute. I saw this in Ander’s talk at //BUILD last year and immediately thought of INotifyPropertyChanged. Essentially, this attribute is applied to an input parameter on a method and the CLR will supply the calling method name as the parameter’s value. As an example, here is a sample INotifyPropertyChanged implementation using this new feature:

public class Person : INotifyPropertyChanged
    private string _name;
    public string Name
        get { return _name; }

            if (_name != value)
                _name = value;
                RaisePropertyChanged(); // note no parameter here!

    public event PropertyChangedEventHandler PropertyChanged = delegate { };
    private void RaisePropertyChanged([CallerMemberName] string propertyName = "")
        PropertyChanged(this, new PropertyChangedEventArgs(propertyName));

Stopping in the debugger, you can see the value of the propertyName parameter:

The performance (at least of .NET 4.5 beta) is in between the unsafe magic string approach and the nice lambda approach – but this is perfectly refactor safe so it’s a nice new way to improve the safety of our code while getting closer to the performance of magic strings with our property change notifications.

This solution also provides for the “all properties have changed” notification by supplying the string – or passing null as the parameter.  If you specifically provide a parameter, then it overrides the <code>[CallerMemberName]</code> attribute and you get that string instead.  So, to raise an “all properties have changed” notification you could do this:

    // or

and to raise a different property altogether you can just pass the magic string as you always have –

  // Callback from some long-running operation
  void OnCalculateSomeValueCompleted()

It’s not the perfect solution however – as you can see above, we still have to use field-backed properties with this approach.  It would be so much nicer to have some compiler support here which calls the <code>RaisePropertyChanged</code> method from an auto-property.  This is done by some frameworks today using an AOP approach, but I’d like to see it with the native toolset.

This is a good step in the right direction though – thanks MSFT!

[EDIT: interestingly enough, I noticed that the latest MSDN example of INotifyPropertyChanged uses this exact approach – see here:

About Mark Smith

Windows systems developer with low-level operating system, threading and .NET experience. For the past several years I have been involved with WPF/Silverlight and most recently iOS and Android. I have worked as an architect and designer for several companies and am particularly interested in client/server and graphical solutions. Specialties:.NET, WPF, Silverlight, Windows, iOS

Latest Blog Posts

Building Windows Store apps with HTML/JS and WinJS

Thanks to everyone who attended the WinJS marathon! Here's the slides and demos we … Read More »

NumericTextBoxBehavior for XAML-based Windows Store Applications

One of the first (and arguably most useful) behaviors that I wrote for MVVMHelpers was a … Read More »