Policy Injection Application Block Deprecated - Alternative Approach

Topics: Exception Handling Application Block, General discussion, Logging Application Block, Policy Injection Application Block
Jun 17, 2012 at 11:55 PM

Hi I've read that the Policy Injection Application Block is a set of legacy components in V5.0 from here...

http://msdn.microsoft.com/en-us/library/ff664572(PandP.50).aspx

What would be the preferable approach for implementing cross-cutting concerns in Enterprise Library 5.0?

Would it be directly using Unity Interception?

Thanks

Andy

Jun 30, 2012 at 7:53 AM

> What would be the preferable approach for implementing cross-cutting concerns in Enterprise Library 5.0?
>
> Would it be directly using Unity Interception?

Yes, that's the answer.

From the Developer's Guide:

[The Policy Injection Application Block] is provided mainly for backwards compatibility with existing applications.

In version 5.0 of Enterprise Library, the recommended approach for implementing policy injection is through the Unity interception mechanism. This supports several different techniques for implementing interception, including the creation of derived classes rather than remoting proxies, and it has much less impact on application performance.

--
Randy Levy
Enterprise Library support engineer
entlib.support@live.com