Deployment and Operations
| Retired Content |
|---|
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. |
Two of an administrator's main tasks will be to plan and manage the initial deployment of the Policy Injection Application Block and to ensure deployment of subsequent updates have minimal impact on existing applications that use the application block. For details of deploying and updating Enterprise Library and the application blocks, see Deploying Enterprise Library.
The Policy Injection Application Block does not include any built-in instrumentation. However, developers, operators, and administrators can use the injection features inherent in the application block, and the handlers provided with it, to add instrumentation features that they may require.
For example, the Logging Application Block provides a wealth of features for capturing execution parameters and call duration, and writing logging information and messages to a range of other applications and formats such as Windows Event Log, Windows Management Instrumentation (WMI), application log files, message queue services, and more. Developers, operators, and administrators can use a Logging Handler to capture information on operation of the application block as it intercepts calls to target classes.
In addition, the Policy Injection Application Block includes the Performance Counter Handler that will capture information when the application block makes calls to target objects. This information can also provide insights into the operation of the Policy Injection Application Block.