Developing Applications Using the Policy Injection Application Block
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
|The latest Enterprise Library information can be found at the Enterprise Library site.|
This topic describes how to develop applications using the Policy Injection Application Block. It explains how to modify the configuration of the application block to perform particular tasks and how to use the application block for particular scenarios, such as creating and accessing target objects for policy injection. This topic assumes that you are using the application block in its original state, without extending it. (To learn how to add functionality, see Extending and Modifying the Policy Injection Application Block.)
This section includes the following topics:
- Entering Configuration Information
- Attribute-based Policy Injection
- Adding Application Code
- Creating an Instance of an Interceptable Target Class
- Accessing Properties and Calling Methods of the Target Class
- Aborted Execution of a Handler Pipeline
- Using Interception with the Policy Injection Application Block Configuration
All application blocks ship as binary assemblies and as source code. If you want to use the source code, you must compile it before you can use the QuickStarts and configuration tools. To learn how to compile the Enterprise Library source code, see Building Enterprise Library from the Source Code.