System.ServiceModel 4.0.0.0 System.ServiceModel.Configuration.TransportElement To be added.

Provides the base class with members common to the and .

- Constructor
  4.0.0.0
  To be added.

  Initializes a new instance of the class.

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

  Applies the settings of this binding element to a specified binding element.

  A binding element that contains the settings to be applied.
- Method
  4.0.0.0
  System.Void `` To be added.

  Copies settings from a specified to this binding element.

  The that contains the values to be copied.
- Property
  4.0.0.0
  System.Configuration.ConfigurationProperty("customDeadLetterQueue", DefaultValue=Mono.Cecil.CustomAttributeArgument, Options=System.Configuration.ConfigurationPropertyOptions.None)
  System.Uri To be added.

  The dead-letter queue is a queue on the queue manager of the sending application for expired messages that have failed to be delivered.

  The URI that is specified by must use the Net.msmq scheme.

  If is set to or , then must be set to null. If is not null, then must be set to .

  Gets or sets a URI that contains the location of the per-application dead-letter queue, where messages that have expired or that have failed transfer or delivery are placed.

- Property
  4.0.0.0
  System.Configuration.ConfigurationProperty("deadLetterQueue", DefaultValue=Mono.Cecil.CustomAttributeArgument, Options=System.Configuration.ConfigurationPropertyOptions.None)
  System.ServiceModel.DeadLetterQueue To be added.

  The dead-letter queue is a queue on the queue manager of the sending application for expired messages that have failed to be delivered. The dead-letter queue enumeration specifies the type of dead-letter queue to use. The values are:

  None: If no dead-letter queue is required. Thus, if a message were to fail delivery, no record of it would be maintained in the dead-letter queue. This is the default value when is set to false.

  System: The system-wide dead-letter queue would be used to record messages that fail delivery. Message Queuing (also known as MSMQ) has a transactional system dead-letter queue and a nontransactional system dead-letter queue to record messages that failed delivery from transactional and nontransactional queues, respectively. This is the default value when is set to true.

  Custom: The queue specified in the is used to record messages that fail delivery.

  The reasons that a message can fail to reach the receiving application include:

  A transactional message is sent to a nontransactional queue.

  A nontransactional message is sent to a transactional queue.

  An unauthenticated message is sent to a queue that accepts only authenticated messages.

  An unencrypted message is sent to a queue that accepts only encrypted messages.

  The message expires before the message is delivered to a receiver.

  The message storage quota of the target computer or the storage quota of the destination queue is exceeded, or there is no available storage space on the target computer when the message arrives.

  The sender does not have the access rights needed to place the message in the destination queue.

  The digital signature attached to the message is not valid.

  An encrypted message cannot be decrypted by the destination queue manager.

  The destination queue is purged or deleted before the message is retrieved.

  Gets or sets an enumeration value that indicates the type of dead-letter queue to use.

- Property
  4.0.0.0
  System.Configuration.ConfigurationProperty("durable", DefaultValue=Mono.Cecil.CustomAttributeArgument, Options=System.Configuration.ConfigurationPropertyOptions.None)
  System.Boolean To be added.

  A durable message survives a queue manager crash, while a volatile message does not. Volatile messages are useful when applications can tolerate occasional lost messages.

  If is set to true, the messages must be durable.

  Gets or sets a value that indicates whether the messages processed by this binding are durable or volatile.

- Property
  4.0.0.0
  System.Configuration.ConfigurationProperty("exactlyOnce", DefaultValue=Mono.Cecil.CustomAttributeArgument, Options=System.Configuration.ConfigurationPropertyOptions.None)
  System.Boolean To be added.

  A message can be sent with or without assurances. An assurance enables an application to ensure that a sent message reached the receiving message queue, or if it did not, the application can determine this by reading the dead-letter queue.

  Messages sent with set to true must be sent only to a transactional queue.

  , when set to true, indicates that Message Queuing (also known as MSMQ) will ensure that a sent message is delivered to the receiving message queue once and only once, and if delivery fails, the message is sent to the dead-letter queue.

  For messages that require to be false, the property defaults to null.

  For messages that require to be true, the property defaults to a transactional system-wide dead-letter queue in Message Queuing.

  Gets or sets a Boolean value that indicates whether messages processed by this binding will be received exactly once.

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

  Initializes this binding element with the content from the specified binding element.

  A binding element that contains the settings to be used to initialize this binding element.
- Property
  4.0.0.0
  System.Configuration.ConfigurationProperty("maxRetryCycles", DefaultValue=Mono.Cecil.CustomAttributeArgument, Options=System.Configuration.ConfigurationPropertyOptions.None)
  System.Configuration.IntegerValidator(ExcludeRange=false, MaxValue=2147483647, MinValue=0)
  System.Int32 To be added.

  A single retry cycle attempts to deliver a message to an application a specified number of times. The number of attempts made is set by the property. If the application fails to consume the message after the attempts at delivery have been exhausted, the message is sent to a retry queue. Subsequent retry cycles consist of the message being returned from the retry queue to the application queue to attempt delivery to the application again, after a delay specified by the property. The property specifies the number of retry cycles that the application uses to attempt to deliver the message.

  Gets or sets the maximum number of retry cycles to attempt delivery of messages to the receiving application.

- Property
  4.0.0.0
  System.Configuration.ConfigurationProperty("msmqTransportSecurity", Options=System.Configuration.ConfigurationPropertyOptions.None)
  System.ServiceModel.Configuration.MsmqTransportSecurityElement To be added. To be added.

  Gets an instance that encapsulates the transport security settings for a binding.

- Property
  4.0.0.0
  System.Configuration.ConfigurationPropertyCollection To be added. To be added.

  Gets a instance that contains a collection of objects that can be attributes or objects of this configuration element.

- Property
  4.0.0.0
  System.Configuration.ConfigurationProperty("receiveErrorHandling", DefaultValue=Mono.Cecil.CustomAttributeArgument, Options=System.Configuration.ConfigurationPropertyOptions.None)
  System.ServiceModel.ReceiveErrorHandling To be added.

  When this property is set to , the channel listener is faulted and a (wrapping a ) is traced and thrown. The offending message is left in the queue and needs to be removed by some manual method. The contains a that can be used to identify and manually remove the offending message from the poison-message queue.

  When this property is set to , the offending message is simply dropped.

  When this property is set to , a negative acknowledgment is sent to the client and the offending message is removed from the poison-message queue. This option is available only on Message Queuing (also known as MSMQ) 4.0.

  When set to , the offending message is moved to the final poison subqueue. This option is available only on Message Queuing 4.0.

  Gets or sets an enumeration value that specifies how poison and nondispatchable messages are handled.

- Property
  4.0.0.0
  System.Configuration.ConfigurationProperty("receiveRetryCount", DefaultValue=Mono.Cecil.CustomAttributeArgument, Options=System.Configuration.ConfigurationPropertyOptions.None)
  System.Configuration.IntegerValidator(ExcludeRange=false, MaxValue=2147483647, MinValue=0)
  System.Int32 To be added.

  If the maximum number of delivery attempts is reached and the message is not consumed by the application, then the message is sent to a retry queue for redelivery at some later point in time. The amount of time before the message is transferred back to the sending queue is controlled by . If retry cycles reach the value, then either the message is sent to the poison-message queue, or a negative acknowledgment is sent back to the sender.

  For more information, see and .

  Gets or sets the maximum number of times that the queue manager should attempt to send a message before transferring it to the retry queue.

- Property
  4.0.0.0
  System.Configuration.ConfigurationProperty("retryCycleDelay", DefaultValue=Mono.Cecil.CustomAttributeArgument, Options=System.Configuration.ConfigurationPropertyOptions.None)
  System.TimeSpan To be added.

  A single retry cycle attempts to deliver a message to a receiving application a specified number of times. The number of attempts made is specified by the property. If the application fails to consume the message after the specified number of immediate retries, the message is sent to a retry queue. Subsequent retry cycles consist of the message being returned from the retry queue to the application queue to attempt delivery to the application again, after a delay specified by the property. The number of retry cycles is specified by the property.

  Gets or sets a value that indicates the time delay between retry cycles when attempting to deliver a message that could not be delivered immediately.

- Property
  4.0.0.0
  System.Configuration.ConfigurationProperty("timeToLive", DefaultValue=Mono.Cecil.CustomAttributeArgument, Options=System.Configuration.ConfigurationPropertyOptions.None)
  System.TimeSpan To be added.

  The property is set to ensure that time-sensitive messages do not become stale before they are processed by the receiving applications. A message in a queue that is not consumed by the receiving application within the time interval specified is said to be expired. Expired messages are sent to a special queue called the dead-letter queue. The location of the dead-letter queue is set with the property or to the appropriate default, based on assurances.

  Gets or sets the interval of time that indicates how long the messages processed by this binding can be in the queue before they expire.

- Property
  4.0.0.0
  System.Configuration.ConfigurationProperty("useMsmqTracing", DefaultValue=Mono.Cecil.CustomAttributeArgument, Options=System.Configuration.ConfigurationPropertyOptions.None)
  System.Boolean To be added.

  When tracing is enabled, report messages are created and sent to the report queue each time the message leaves or arrives at a computer running Message Queuing (also known as MSMQ).

  Gets or sets a Boolean value that indicates whether messages processed by this binding should be traced.

- Property
  4.0.0.0
  System.Configuration.ConfigurationProperty("useSourceJournal", DefaultValue=Mono.Cecil.CustomAttributeArgument, Options=System.Configuration.ConfigurationPropertyOptions.None)
  System.Boolean To be added.

  Queued applications that must keep a record of messages that have left the computer's outgoing queue can copy the messages to a journal queue. Once a message leaves the outgoing queue and an acknowledgment is received that the message was received on the destination computer, a copy of the message is kept in the sending computer's system journal queue.

  Gets or sets a Boolean value that indicates whether copies of messages processed by this binding should be stored in the source journal queue.