Policy Injection Matching Rules

Unity includes matching rule implementations that provide a wide range of capabilities for selecting the objects and their members to which Unity will add a handler pipeline. Interception policies use the matching rules to define which methods will be intercepted.

A matching rule is essentially a predicate that Unity checks each time it intercepts object creation. If all of the specified matching rules evaluate to True for any particular invocation, the application block will create and add the handler pipeline for that policy. If any one of the matching rules does not evaluate to true, Unity generates an instance of the original object or a derived object, and does not create a proxy or a handler pipeline.

The following table lists the matching rules provided with Unity, and summarizes their use and parameters.

The following sections describe the built-in matching rules in detail:

• The Assembly Matching Rule
• The Custom Attribute Matching Rule
• The Member Name Matching Rule
• The Method Signature Matching Rule
• The Namespace Matching Rule
• The Parameter Type Matching Rule
• The Property Matching Rule
• The Return Type Matching Rule
• The Tag Attribute Matching Rule
• The Type Matching Rule

You can also create and use custom matching rules. For more information, see Creating Policy Injection Matching Rules. For information about using interception, see Using Interception and Policy Injection.

Next Topic | Previous Topic | Home | Community