Comments on: Easier PropertyChanged notification with PostSharp http://graemehill.ca/easier-propertychanged-notification-with-postsharp Fri, 30 Jul 2010 13:24:41 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Graeme http://graemehill.ca/easier-propertychanged-notification-with-postsharp/comment-page-1#comment-695 Graeme Sat, 19 Jun 2010 19:44:53 +0000 http://graemehill.ca/?p=91#comment-695 Good to know. Thanks. Good to know. Thanks.

]]> By: Phil Kan http://graemehill.ca/easier-propertychanged-notification-with-postsharp/comment-page-1#comment-671 Phil Kan Wed, 02 Jun 2010 03:11:57 +0000 http://graemehill.ca/?p=91#comment-671 The MVVM Foundation code on codeplex contains such a method, so we don't need to define it directly. See the ObservableObject in http://mvvmfoundation.codeplex.com/. Unfortunately, that implementation only validates the property name in debug builds. I would assume then, that given the right references, the NotifyAttribute could be implemented to call the RaisePropertyChanged(string) method instead of the custom implementation. The MVVM Foundation code on codeplex contains such a method, so we don’t need to define it directly. See the ObservableObject in http://mvvmfoundation.codeplex.com/. Unfortunately, that implementation only validates the property name in debug builds.

I would assume then, that given the right references, the NotifyAttribute could be implemented to call the RaisePropertyChanged(string) method instead of the custom implementation.

]]> By: Verify your property names in INotifyPropertyChanged implementation | Graeme Hill on .NET development http://graemehill.ca/easier-propertychanged-notification-with-postsharp/comment-page-1#comment-14 Verify your property names in INotifyPropertyChanged implementation | Graeme Hill on .NET development Sun, 23 Aug 2009 17:12:31 +0000 http://graemehill.ca/?p=91#comment-14 [...] I have posted another article here that explains what I think is a better solution to this problem using a simple PostSharp [...] [...] I have posted another article here that explains what I think is a better solution to this problem using a simple PostSharp [...]

]]>