Comments on: INotifyPropertyChanged with PostSharp 1.5

By: TimothyP

TimothyP — Mon, 22 Aug 2011 05:37:13 +0000

Thnx for the example… seen other examples out there much more complicated to start out with. One thing I’d like to note is that you could use “dynamic instance = args.Instance;” to expand the use to anything that has an OnPropertyChanged(string); method. For example I have objects that need change notification.

By: INotifyPropertyChanged with custom targets

INotifyPropertyChanged with custom targets — Tue, 24 May 2011 08:48:03 +0000

[…] can use PostSharp for that, you should at least use lambda expressions instead of […]

By: Blog » Blog Archive » INotifyPropertyChanged with lambdas

Blog » Blog Archive » INotifyPropertyChanged with lambdas — Tue, 16 Feb 2010 21:48:27 +0000

[…] One that I particularly like is by using PostSharp to implement INotifyPropertyChanged. […]

By: Limilabs support

Limilabs support — Tue, 15 Sep 2009 21:04:09 +0000

In reply to Marcin Obel.

Yes, you can put the attribute on the class level.
In such case all class properties will raise appropriate PropertyChanged events.

Although I think that in PostSharp 1.5 it can not be the base class – PostSharp attributes are not inherited.

By: Marcin Obel

Marcin Obel — Tue, 15 Sep 2009 19:11:16 +0000

Does the PostSharp allow to put such attribute on class definition instead of property?
It would be nice to have this attribute on base ViewModel and nothing on properties (less work and convention over configuration at the same time).