System.ServiceModel 4.0.0.0

To explicitly control the behavior of the application when an exception is thrown, implement the interface and add it to the ’s property. enables you to explicitly control the SOAP fault generated, decide whether to send it back to the client, and perform associated tasks, such as logging. Error handlers are called in the order in which they were added to the property.

Implement the method to control the fault message that is returned to the client.

Implement the method to ensure error-related behaviors, including error logging, assuring a fail fast, shutting down the application, and so on.

Because the method can be called from many different places there are no guarantees made about which thread the method is called on. Do not depend on method being called on the operation thread.

All implementations are called first, prior to sending a response message. When all implementations have been called and return, and if is non-null, it is sent back to the client according to the operation contract. If is null after all implementations have been called, the response message is controlled by the property value.

Exceptions can occur after all implementations are called and a response message is handed to the channel. If a channel exception occurs (for example, difficulty serializing the message) objects are notified. In this case, you should still make sure that your development environment catches and displays such exceptions to you or makes use of tracing to discover the problem. For more information about tracing, see Using Tracing to Troubleshoot Your Application.

After the response message has been sent, all implementations are called in the same order.

Typically, an implementation is added to the property on the service (and the client in the case of duplex communication).

You can add the to the runtime by implementing a behavior (either an , , , or object) and use the behavior programmatically, from a configuration file or with a custom attribute to attach your .

For more information about using behaviors to modify the runtime, see Attaching Extensions Using Behaviors.

Allows an implementer to control the fault message returned to the caller and optionally perform custom error processing such as logging.

- Method
  4.0.0.0
  System.Boolean `` To be added.

  Use the method to implement error-related behaviors such as error logging, system notifications, shutting down the application, and so on, and return a value that specifies whether the exception has been handled appropriately.

  Because the method can be called from many different places there are no guarantees made about which thread the method is called on. Do not depend on method being called on the operation thread.

  All implementations are called. By default (when the return value is false), if there is an exception, the dispatcher aborts any session and aborts the if the is anything other than . The exception is then considered unhandled and any state is considered corrupt.

  Return true from to prevent this default behavior. If any error handler returns true it instructs indigo2 that it is safe to continue using state associated with the failed request.

  If no error handler returns true from the method the exception is considered unhandled and the default response applies, potentially resulting in an aborted and channel when communicating on a session channel or the property is not set to .

  The parameter is never null and contains the exception object that was thrown.

  Enables error-related processing and returns a value that indicates whether the dispatcher aborts the session and the instance context in certain cases.

  true if indigo1 should not abort the session (if there is one) and instance context if the instance context is not ; otherwise, false. The default is false.

- Method
  4.0.0.0
  System.Void `` `` `` To be added. To be added. To be added. To be added. To be added.