Back here I made a quick and dirty performance comparison. In the comments I actually got some "flak" scrutinizing some of the "design decisions" behind the example shown. I would like to reinstate
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.
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 behaviou
The other day I got a presentation on Spring.NET and that it brings along quite a bit of aspect oriented Zen. Frankly, I do not know much about Spring.NET. I did a very quick look at performance co