All good questions. Unity and Interception are two topics in the documentation which are being finalized now. That's the reason the current doc set is labeled as "Pre-release" and posted on Codeplex only and not MSDN. As soon as the final editorial
and content pass on these are completed, we'll release the full set of docs on MSDN (hopefully next week).
In v5, the interception mechanism is provided by Unity and PIAB now is mainly a collection of handlers. So, yes, you can still use the AuthorizationCallHandler, ExceptionCallHandler and the like. Interception can be configured
both programmatically and through the Policy Injection settings in the config tool. All Matching Rules, Policies and Call Handlers still apply in PIAB.
While the Policy Injection Application Block is still included in this release of Enterprise Library, it is (with the exception of one call handler - Performance Counter Handler) a set of legacy components such as the PolicyInjection facade that supports
backwards compatibility with applications that use versions of Enterprise Library prior to version 5.0.
Also be aware that, even if you decide to continue to use the call handlers included in the Policy Injection Application Block, you must still make some changes to your existing application. The location of the call handlers has changed,
so you must ensure that you reference the appropriate assemblies and namespaces in your code (see the
Notice that the Unity interception is more powerful than earlier versions of PIAB and supports both instance and type interceptors.
For new, custom call handlers and interceptors, you should consider the "raw interception" of Unity 2.0.
Hope this helps.
Also, I'd like to mention that the EntLib team is working on a new set of hands-on labs, and the topic of interception is certainly included in it with detailed walk-throughs and exercises. We plan to release these shortly.