Compare to PostSharp?

Feb 23, 2009 at 4:35 PM
How will this approach hold up against PostSharp? I am no supergeek, but I imagine that the post-compile approach that PostSharp takes will give you a lot better performance than doing run-time intercepts.

In my case, the most likely approach would be to add performance counters to a bunch of critical methods throughout my system (transaction engine in a financial system), and I wouldn't want to spend a lot of time tuning my code down to each transaction taking 2-3 ms and then adding 2 ms for AOP-ing my performance counters...

Any comments?
Feb 23, 2009 at 9:01 PM
I've only looked at postsharp briefly.
The main difference is that postsharp only allows you to intercept and change behavior of code under your control (you have to put attributes on it and compile)

CThru will working with any existing codebase (a-la silverlight assemblies like in SilverUnit or Sharepoint code) and also change its behavior even if it was not compiled with any AOP behavior.