Thanks Sergey,

Actually, I kind of hope they provide both behaviours. The old behaviour was nice for creating light-weight test scaffolding (one could override return values from any method of a class without touching the class's source code).

And the new behaviour is nice for simply "spying" on an object without changing its behaviour, again, without touching the source of the class.

Either way, I think there are use-cases for being able to fire delegate code both before and after an event/method without the cannonical RAISEEVENT() calls.

I'm sure they'll take careful note of my wishes when I call.... <s>

-lc