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...