System.ServiceModel 4.0.0.0 Implement the interface on a object to write statements about endpoint capabilities or requirements into the WSDL information exposed by a particular endpoint. Typically the binding element is one that implements some feature, but this is not required. To load your policy exporter from a configuration file, implement a that returns the policy exporter object. The policy exporter is used by indigo1 to use policy assertions to communicate to clients the existence of that custom binding requirement or endpoint capability. The method takes the and objects. Use the , , and methods to obtain collections of policy assertions that have already been exported at various scopes. Then add your custom policy assertion object to the appropriate collection. The property exposes the for the endpoint that is being exported. This allows the extension to correctly scope their exported policy assertions. For example, security attributes in code may add behaviors to the that indicate where security policy assertions should be added. The mechanism only supports exporting policy assertions in WSDL. To export custom WSDL elements you must use the mechanism to modify the WSDL directly. Once custom policy assertions have been attached to the WSDL information, clients can detect and import the custom binding assertions by using an object.

Implement to insert custom binding policy assertions in the Web Services Description Language (WSDL) information.

Method 4.0.0.0 System.Void Use the , , and methods to obtain collections of policy assertions that have already been exported at various scopes. Then add your object to the appropriate collection.

Implement to include for exporting a custom policy assertion about bindings.

The that you can use to modify the exporting process. The that you can use to insert your custom policy assertion.