Click here to Skip to main content
Click here to Skip to main content
Go to top

INotifyPropertyChanged Revisited with .NET Framework 4.5

, 8 Feb 2014
Rate this:
Please Sign up or sign in to vote.
INotifyPropertyChanged revisited with .NET Framework 4.5

Introduction

Prior to this post, I have already discussed few ways of handling INotifyPropertyChanged interface. Now you might be thinking what's next? 

Well, today I'll talk about a much better and cleaner way of handling this interface, which is type-safe as well as less error prone. Till now, as a common practice, we were passing a property name as a parameter of our RaisedPropertyChanged method, which unfortunately has some demerits.

Let's say, what if user changed the name of the property and forgot to change the parameter passed inside RaisedPropertyChanged method. Now you might say that we can get rid of this by using Reflection. Even I agree with that, but again it comes with an additional associated cost. So, what's the solution now???

Enough of worries, this issue has been addressed in .NET 4.5, in which the developer can get rid of this parameter passing approach. Impressed?
An attribute titled CallerMemberName relieves us from all the worries because now this attribute will retrieve method and property name for us. Let's have a look at the code now.

Using the Code

public class ViewModelBase : INotifyPropertyChanged
    {

        public event PropertyChangedEventHandler PropertyChanged;
        protected void RaisePropertyChanged([CallerMemberName]string propertName="")
        {
            var temp = PropertyChanged;
            if (temp != null)
            {
                temp(this, new PropertyChangedEventArgs(propertName));
            }
        }
    } 

You will notice that the attribute is applied with the parameters supplied for RaisedPropertyChanged method. So, now the implementation of our property will be lot simpler as:

 private string _employeeName;
        public string EmployeeName
        {
            get { return _employeeName; }
            set
            {
                if (_employeeName != value)
                {
                    _employeeName = value;
                    RaisePropertyChanged();
                }
            }
        } 

Now user is not forced to pass parameter to this RaisedPropertyChanged method. Hope you enjoyed learning this new feature.

Previous Post

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

Shweta Lodha
Technical Lead
India India
You can also follow me at my blog http://www.shwetalodha.blogspot.in/
Follow on   Twitter

Comments and Discussions

 
Questionother Properties PinmemberSami Abdelgadir9-Feb-14 23:59 
AnswerRe: other Properties Pinmemberjohannesnestler10-Feb-14 0:32 
AnswerRe: other Properties PinmemberShweta Lodha10-Feb-14 7:26 
QuestionRe: other Properties PinmemberMember 98192705-Sep-14 5:35 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Mobile
Web04 | 2.8.140926.1 | Last Updated 8 Feb 2014
Article Copyright 2014 by Shweta Lodha
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid