Scenarios and Goals

The Policy Injection Application Block addresses the following scenarios:

• Building applications from objects that require encapsulation and separation to provide the most benefit from independence in operation, and the maximum capability for reuse
• Managing crosscutting concerns that may otherwise affect the independence of objects that require access to common features (such as logging or validation)
• Allowing the developer and administrator to configure the behavior of objects in an application through configuration, by adding or removing handlers that execute common tasks or add custom features
• Minimizing the work required and the code that the developer must write to perform common tasks within an application, such as logging, validation, authorization, and instrumentation
• Making it easy for developers to take advantage of features within the Enterprise Library Core and individual application blocks that implement tasks commonly required in enterprise applications
• Reducing development time and cost, and minimizing bugs in complex applications that use common and shared tasks and services