tag:blogger.com,1999:blog-416560600691994772.post1306813359520250318..comments2022-01-13T19:30:16.412+00:00Comments on PaVZaV's blog: Interception and ServiceLocator in UnityUnknownnoreply@blogger.comBlogger1125tag:blogger.com,1999:blog-416560600691994772.post-5194476288720074572012-10-17T22:39:11.292+01:002012-10-17T22:39:11.292+01:00Unity is great - so long as it's used properly...Unity is great - so long as it's used properly! This looks like a really good way to use Interception.<br /><br />Conversely, working in a very different environment, I'm finding myself leveraging CompilerServices to dynamically build and compile wrapper classes at runtime that log Pre and Post messages around each call, this enabling diagnostic logging including method call timings without having to rebuild the app to strip out the non-performant debug code. Something else you might be interested in is the .Net 4 CallerMemberNameAttribute and its siblings. (If you're wondering what I use instead of Unity, I've got my own dead simple IoC container.)Anonymoushttps://www.blogger.com/profile/07356356301592206178noreply@blogger.com