Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Possible Duplicate:
Why does C# require you to write a null check every time you fire an event?
I see often the following code but somehow don’t get it.
if (PropertyChanged != null)
PropertyChanged(this, new PropertyChangedEventArgs("UIState"));
Why do i need to check if the event is null before rasing it. All of the time, at least when I try it, I can get away with just raising the event.
It has nothing to do with INotifyPropertyChanged. Any event that has no event handlers registered can be null, and if you try to call PropertyChanged (or any event) when it is null you will get a NullReferenceException.
There is no guarantee that PropertyChanged will never be null. It just so happens that you’ve always called it when an event handler was registered.