Comments on: The bare bones of Unity interceptions http://visualizationtools.net/default/the-bare-bones-of-unity-interceptions/ Think. Visualize. Understand. Wed, 28 Dec 2011 13:39:14 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jeremy Regan http://visualizationtools.net/default/the-bare-bones-of-unity-interceptions/#comment-199 Jeremy Regan Sun, 07 Dec 2008 00:07:50 +0000 http://www.orbifold.net/default/?p=1215#comment-199 This was helpful. The MSDN documentation leaves a lot to be desired for working examples such as you have provided. My only wish is that you had also provided the corresponding XML configuration for the policies that you used. To note, this interception mechanism leaves a lot to be desired in terms of implementation details. The .NET type system is not smart enough to know if you injected one type if it is inherited by another object registered in the container which is subject to interception. This is not a convolved example either; consider the case of a service layer with a base interface as the constructor argument. Even if multiple child interfaces inherit from it, each must register its policy to be subject to interception. Compared to Spring or Castle AOP, this is immature and aggravating to use. I suspect over time it will become better but it is lacking and shows how Microsoft cannot truly innovate, and still lag behind on some modern enterprise concepts that have been in use for years. This was helpful. The MSDN documentation leaves a lot to be desired for working examples such as you have provided. My only wish is that you had also provided the corresponding XML configuration for the policies that you used.

To note, this interception mechanism leaves a lot to be desired in terms of implementation details. The .NET type system is not smart enough to know if you injected one type if it is inherited by another object registered in the container which is subject to interception. This is not a convolved example either; consider the case of a service layer with a base interface as the constructor argument. Even if multiple child interfaces inherit from it, each must register its policy to be subject to interception. Compared to Spring or Castle AOP, this is immature and aggravating to use. I suspect over time it will become better but it is lacking and shows how Microsoft cannot truly innovate, and still lag behind on some modern enterprise concepts that have been in use for years.

]]> By: Vladimir Kofman http://visualizationtools.net/default/the-bare-bones-of-unity-interceptions/#comment-198 Vladimir Kofman Wed, 26 Nov 2008 13:31:06 +0000 http://www.orbifold.net/default/?p=1215#comment-198 Thanks for this article! Exactly what I've been looking for. Thanks for this article! Exactly what I’ve been looking for.

]]>