With all of the substitution patterns, the principle is that the proxied target doesn't need to be aware of the proxying object.  That's pretty achievable if what you're trying to do is provide a local proxy to a remote object.  However, when you're using a decorator, things get a bit trickier.  Welcome to the "leaking this" problem. To start with an easy example, what if the target does this: return this; What do you do?  Well, it's not obvious, but typically you'll get the decorator to return itself.  This case...

This is a straight plug, but I've got to say, I'm really enjoying reading Krzysztof Koźmic's blog at the moment.  In particular, his guide to Dynamic Proxy is excellent.  I've certainly learned a lot by reading it.  I've said before that dynamic proxy is extremely powerful and useful.  It's good to see someone who properly understands it giving such a lucid step by step guide to how to use it.  Me, whether or not I keep working on AutoGen, I'll definitely keeping working with DP.  Sadly, it's still quite hard to find on google.  Let's hope this post improves that...

One of the nice things about finally finishing a major project is that you get to do some work on side projects you find entertaining.  So, today, I finally finished a rather ugly merge and got a new version of AutoGen for Castle out.  Obviously, it isn't hard to implement the Common Service Locator in Windsor.  However, since the idea of AutoGen was to allow you to use your own abstraction for DI, and so implementing Microsoft's seemed like a good stress test.  I'll take a crack at NServiceBus next... :) I shamelessly ripped off Ayende's tests for the CSL...

Mauricio Scheffer asked how AutoGen differs from the TypedFactory Facility already in Castle.  (An equally valid question is why the code is five times the size.)  The answer is that it doesn't in essence, but it does in detail.  However, the details matter, in that AutoGen addresses common use cases, whereas the TypedFactoryFacility is only going to save you 6 lines of code.  The principal differences are: Configuration Constructor Arguments Handling Keys Disposal Handling Multiple Methods How TypedFactoryFacility is used Let's take...

I recently published a tool called AutoGen for Castle.  You can check it out at Google Code.  In essence, it auto-generates factory objects for you and adds them to your container.  This is an extremely useful thing to be able to do.  I do, however, find it a bit hard to explain, so bear with me. A relatively good rule of thumb these days is that a class should instantiate objects or do something with objects but never both.  Miško Hevery has written a lot of good stuff on this subject, and I don't propose to mangle his thinking here. ...