There is a new drop of Unity v1.2 dated September 29th on CodePlex.
I haven't had a chance to play with it yet, but based on a bit of browsing in the source code I noticed a few name changes and additions.
First, if you have watched my recent screecast:
It looks like the RemotingPolicyInjector has been renamed to TransparentProxyPolicyInjector. Please take this into consideration when viewing the screencast and attempting to write similar code yourself. You will find the TransparentProxyPolicyInjector within the source code in a folder called TransparentProxyInterception, which is the interception method used in the Enterprise Library Policy Injection Application Block.
There also appears to be a new assembly, called Unity.Interception.Configuration, which holds all the configuration doodads for wiring up interception in your App.config or Web.config files.
- CallHandlerConfigurationElement
- CallHandlerConfigurationElementCollection
- DefaultTransparentProxyInjectorConfigurationElement
- InterceptionConfigurationElement
- InterceptionPolicyConfigurationElement
- InterceptionPolicyConfigurationElementCollection
- MatchingRuleConfigurationElement
- MatchingRuleConfigurationElementCollection
- PolicyElementConfigurationElement
- RuleDrivenPolicyElementConfigurationElement
- TransparentProxyInjectorConfigurationElement
- TransparentProxyInjectorConfigurationElementBase
- TransparentProxyInjectorConfigurationElementCollection
- TransparentProxyInjectorKey
Again, I expect all this works the same as the Policy Injection Application Block.
When I get a chance, I will write up a quick example using the TransparentProxyPolicyInjector just to keep things as current as possible.
Note that we are on the bleeding edge here of understanding Unity Interception, so no doubt things will continue to change before Unity v1.2 ships. Therefore, expect that some of these tutorials and samples may need to be adjusted appropriately based on name and code changes that we experience from drop to drop.
Unity 1.2 Tutorials: