NotificationObject & UnaryMember

Topics: Prism v4 - Silverlight 4
Jul 22, 2011 at 4:09 PM

I've seen numerous implementations of the INotifyPropertyChanged ( that have support for the UnaryExpression in addition to the MemberExpression.  Examples of the UnaryExpression include uses of unary operators within the expression such as,

RiasePropertyChanged(() => !MyPropertyName);

Is there reason enough to warrant its inclusion?  I had supposed the support for the UnaryExpression is because you could extract the MemberExpression from this. 

Does the community have any pro/cons related this this implementation as it differs from the Prism NotificationObject?

Jul 22, 2011 at 5:47 PM


If you consider an implementation supporting UnaryExpressions should be added to the Prism Library, you could create a work item in the Issue Tracker, so that the product team considers it for future versions.

Other than that, the community is encouraged to post their notions of pros/cons of including that.

I hope you find this helpful.

Guido Leandro Maliandi

Jul 22, 2011 at 9:47 PM

It's those notions that I'm interested.  I have not seen a use case supporting the UnaryExpression support even though I see it implemented in many samples.  Fingers crossed someone here knows of one...