Remember the Epic fail that was building a simple class and a proxy on top to save on doing the PropertyChanged-mechanics? It now works in WPF, too, which, I hope you'll agree, is pretty cool. After some research I found in the Discussion Forum of the Castle team that the issue cropped up beforehand...

It seemed a straightforward thing to do. Sending property changed events when a property is changed is repetitive boilerplate code that can be factored out into an aspect of your system's behaviour. This can be done with a proxy generator library like the Castle's DynamicProxy2 (See my first...