diff --git a/xml/System.ServiceModel.Activation/ServiceHostFactory.xml b/xml/System.ServiceModel.Activation/ServiceHostFactory.xml
index a1deed43af2..53497b4d88a 100644
--- a/xml/System.ServiceModel.Activation/ServiceHostFactory.xml
+++ b/xml/System.ServiceModel.Activation/ServiceHostFactory.xml
@@ -29,23 +29,23 @@
Factory that provides instances of in managed hosting environments where the host instance is created dynamically in response to incoming messages.
- , consider also implementing a factory that derives from the class.
-
- If you have implemented a custom derivative of instead, then consider also implementing a factory that derives your factory from directly.
-
-
-
-## Examples
- This examples show how to use the class:
-
+ , consider also implementing a factory that derives from the class.
+
+ If you have implemented a custom derivative of instead, then consider also implementing a factory that derives your factory from directly.
+
+
+
+## Examples
+ This examples show how to use the class:
+
:::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/servicehostfactory/cs/program.cs" id="Snippet0":::
- :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_CFX/servicehostfactory/vb/program.vb" id="Snippet0":::
-
+ :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_CFX/servicehostfactory/vb/program.vb" id="Snippet0":::
+
]]>
@@ -69,14 +69,14 @@
Initializes a new instance of the class.
- :
-
+ :
+
:::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/servicehostfactory/cs/program.cs" id="Snippet1":::
- :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_CFX/servicehostfactory/vb/program.vb" id="Snippet1":::
-
+ :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_CFX/servicehostfactory/vb/program.vb" id="Snippet1":::
+
]]>
@@ -119,14 +119,14 @@
Creates a with specific base addresses and initializes it with specified data.
A with specific base addresses.
- method:
-
+ method:
+
:::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/servicehostfactory/cs/program.cs" id="Snippet3":::
- :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_CFX/servicehostfactory/vb/program.vb" id="Snippet3":::
-
+ :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_CFX/servicehostfactory/vb/program.vb" id="Snippet3":::
+
]]>
@@ -163,13 +163,13 @@
Creates a for a specified type of service with a specific base address.
A for the type of service specified with a specific base address.
- method:
-
-
-
+ method:
+
+
+
]]>
diff --git a/xml/System.ServiceModel.Activities.Configuration/SendMessageChannelCacheElement.xml b/xml/System.ServiceModel.Activities.Configuration/SendMessageChannelCacheElement.xml
index 478b78efbc4..46e963584e0 100644
--- a/xml/System.ServiceModel.Activities.Configuration/SendMessageChannelCacheElement.xml
+++ b/xml/System.ServiceModel.Activities.Configuration/SendMessageChannelCacheElement.xml
@@ -67,11 +67,11 @@
if the workflow instance cache is turned on; otherwise, .
- back on which requires them to carefully read the appropriate MSDN document and make a decision that strikes a balance between security and performance.
-
+ back on which requires them to carefully read the appropriate MSDN document and make a decision that strikes a balance between security and performance.
+
]]>
@@ -171,11 +171,11 @@
Gets or sets the settings of the channel factory cache.
The settings of the channel factory cache.
- and .
-
+ and .
+
]]>
diff --git a/xml/System.ServiceModel.Activities/ReceiveContent.xml b/xml/System.ServiceModel.Activities/ReceiveContent.xml
index 303b0a9997d..463694dc802 100644
--- a/xml/System.ServiceModel.Activities/ReceiveContent.xml
+++ b/xml/System.ServiceModel.Activities/ReceiveContent.xml
@@ -16,13 +16,13 @@
An abstract base class for classes that represent the data received by a workflow service.
- class to specify the content for a activity.
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/contentbasedcorrelation/cs/client.cs" id="Snippet3":::
-
+ class to specify the content for a activity.
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/contentbasedcorrelation/cs/client.cs" id="Snippet3":::
+
]]>
@@ -59,13 +59,13 @@
Creates a new instance with the specified message.
A instance.
- method to specify the content for a activity.
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/contentbasedcorrelation/cs/client.cs" id="Snippet3":::
-
+ method to specify the content for a activity.
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/contentbasedcorrelation/cs/client.cs" id="Snippet3":::
+
]]>
diff --git a/xml/System.ServiceModel.Activities/SendMessageChannelCache.xml b/xml/System.ServiceModel.Activities/SendMessageChannelCache.xml
index 11332097abe..6e0fadb64b7 100644
--- a/xml/System.ServiceModel.Activities/SendMessageChannelCache.xml
+++ b/xml/System.ServiceModel.Activities/SendMessageChannelCache.xml
@@ -20,22 +20,22 @@
Represents an extension that enables the customization of the cache sharing levels, the settings of the channel factory cache, and the settings of the channel cache for workflows that send messages to service endpoints using messaging activities.
- .
-
- By default, in a workflow hosted by a , the cache used by messaging activities is shared across all workflow instances in the (host-level caching). For a client workflow that is not hosted by a , the cache is available only to the workflow instance (instance-level caching). Caching is disabled by default for any send activity in your workflow that has endpoints defined in configuration.
-
- For more information about how to change the default cache sharing levels and cache settings for the channel factory and channel cache, see [Changing the Cache Sharing Levels for Send Activities](/dotnet/framework/wcf/feature-details/changing-the-cache-sharing-levels-for-send-activities).
-
-
-
-## Examples
- The following example shows how to use the class to share a channel cache between two workflow applications in a single app domain.
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/channelcache/cs/client.cs" id="Snippet0":::
-
+ .
+
+ By default, in a workflow hosted by a , the cache used by messaging activities is shared across all workflow instances in the (host-level caching). For a client workflow that is not hosted by a , the cache is available only to the workflow instance (instance-level caching). Caching is disabled by default for any send activity in your workflow that has endpoints defined in configuration.
+
+ For more information about how to change the default cache sharing levels and cache settings for the channel factory and channel cache, see [Changing the Cache Sharing Levels for Send Activities](/dotnet/framework/wcf/feature-details/changing-the-cache-sharing-levels-for-send-activities).
+
+
+
+## Examples
+ The following example shows how to use the class to share a channel cache between two workflow applications in a single app domain.
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/channelcache/cs/client.cs" id="Snippet0":::
+
]]>
@@ -99,20 +99,20 @@
The cache settings for cached channels.
Initializes a new instance of the class with custom factory cache and channel cache settings.
- and .
-
- You can choose to use only the channel factory cache and disable the channel cache by passing the `channelSettings` parameter to this constructor initialized to a instance with a value of 0. To disable the cache completely for both the channel factory cache and the channel cache, pass the `factorySettings` parameter to this constructor initialized to a instance with a value of 0. Note that you cannot turn the channel cache on if the channel factory cache is disabled.
-
-
-
-## Examples
- The following example shows how to use the class to share a channel cache between two workflow applications in a single app domain.
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/channelcache/cs/client.cs" id="Snippet0":::
-
+ and .
+
+ You can choose to use only the channel factory cache and disable the channel cache by passing the `channelSettings` parameter to this constructor initialized to a instance with a value of 0. To disable the cache completely for both the channel factory cache and the channel cache, pass the `factorySettings` parameter to this constructor initialized to a instance with a value of 0. Note that you cannot turn the channel cache on if the channel factory cache is disabled.
+
+
+
+## Examples
+ The following example shows how to use the class to share a channel cache between two workflow applications in a single app domain.
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/channelcache/cs/client.cs" id="Snippet0":::
+
]]>
@@ -141,13 +141,13 @@
to turn caching on; otherwise, .
Initializes a new instance of the class with custom factory cache settings, custom channel cache settings, and a value that indicates whether to turn caching on.
- activities that don't use endpoints defined in configuration. However, if you want to turn caching on in this case call this constructor with the `allowUnsafeCaching` parameter set to `true`. Next, add the new instance of this class as an extension to a workflow service host or a workflow instance.
-
- For more information about channel factories, see and .
-
+ activities that don't use endpoints defined in configuration. However, if you want to turn caching on in this case call this constructor with the `allowUnsafeCaching` parameter set to `true`. Next, add the new instance of this class as an extension to a workflow service host or a workflow instance.
+
+ For more information about channel factories, see and .
+
]]>
@@ -178,11 +178,11 @@
to turn caching on; otherwise, .
- activity in your workflow has endpoints defined in configuration caching could be unsecure and therefore is disabled by default. However, if you want to turn caching on set this property to `true`.
-
+ activity in your workflow has endpoints defined in configuration caching could be unsecure and therefore is disabled by default. However, if you want to turn caching on set this property to `true`.
+
]]>
@@ -263,11 +263,11 @@
Gets or sets the settings of the channel factory cache.
The settings of the channel factory cache.
- and .
-
+ and .
+
]]>
diff --git a/xml/System.ServiceModel.Activities/WorkflowControlClient.xml b/xml/System.ServiceModel.Activities/WorkflowControlClient.xml
index 8504c189117..0334c0eae43 100644
--- a/xml/System.ServiceModel.Activities/WorkflowControlClient.xml
+++ b/xml/System.ServiceModel.Activities/WorkflowControlClient.xml
@@ -19,11 +19,11 @@
Allows a client to send control operations to a workflow service hosted with .
-
@@ -79,13 +79,13 @@
The workflow control endpoint.
Initializes a new instance of the class with the specified .
- instance using this constructor.
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet2":::
-
+ instance using this constructor.
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet2":::
+
]]>
@@ -115,13 +115,13 @@
The configuration to use.
Initializes a new instance of the class with the specified endpoint configuration.
-
@@ -153,13 +153,13 @@
The workflow control endpoint.
Initializes a new instance of the class with the specified binding, and .
-
@@ -191,13 +191,13 @@
The endpoint address.
Initializes a new instance of the class with the specified endpoint configuration and .
-
@@ -229,13 +229,13 @@
The endpoint address.
Initializes a new instance of the class with the specified endpoint configuration and endpoint address.
-
@@ -277,13 +277,13 @@
The workflow instance to abandon.
Abandons the specified workflow instance.
- .
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet6":::
-
+ .
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet6":::
+
]]>
@@ -312,13 +312,13 @@
The reason to abandon the workflow instance.
Abandons the specified workflow instance.
- .
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet7":::
-
+ .
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet7":::
+
]]>
@@ -797,13 +797,13 @@
The workflow instance to cancel.
Cancels the specified workflow instance.
- .
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet8":::
-
+ .
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet8":::
+
]]>
@@ -1060,13 +1060,13 @@
The workflow instance to run.
Runs the specified workflow instance.
- .
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet9":::
-
+ .
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet9":::
+
]]>
@@ -1188,13 +1188,13 @@
The workflow instance to suspend.
Suspends the specified workflow instance.
- .
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet10":::
-
+ .
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet10":::
+
]]>
@@ -1223,13 +1223,13 @@
The reason to suspend the workflow instance.
Suspends the specified workflow instance.
- .
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet11":::
-
+ .
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet11":::
+
]]>
@@ -1405,13 +1405,13 @@
The workflow instance to terminate.
Terminates the specified workflow instance.
- .
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet12":::
-
+ .
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet12":::
+
]]>
@@ -1440,13 +1440,13 @@
The reason to terminate the workflow instance.
Terminates the specified workflow instance with the specified reason.
- .
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet13":::
-
+ .
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet13":::
+
]]>
@@ -1613,13 +1613,13 @@
The workflow instance to unsuspend.
Unsuspends the specified workflow instance.
- method.
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet1":::
-
+ method.
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/managementendpoint/cs/client.cs" id="Snippet1":::
+
]]>
diff --git a/xml/System.ServiceModel.Activities/WorkflowCreationContext.xml b/xml/System.ServiceModel.Activities/WorkflowCreationContext.xml
index 38f39f92127..b1855c27073 100644
--- a/xml/System.ServiceModel.Activities/WorkflowCreationContext.xml
+++ b/xml/System.ServiceModel.Activities/WorkflowCreationContext.xml
@@ -138,13 +138,13 @@
Aborts the .
- method.
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/wfcreationcontext/cs/program.cs" id="Snippet2":::
-
+ method.
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/wfcreationcontext/cs/program.cs" id="Snippet2":::
+
]]>
@@ -182,13 +182,13 @@
Begins an asynchronous operation to perform workflow instance completion notification. This method is called when the workflow instance associated with this completes. Derived classes can override this operation to perform custom actions on workflow instance completion.
The status of the asynchronous operation.
- method.
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/wfcreationcontext/cs/program.cs" id="Snippet0":::
-
+ method.
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/wfcreationcontext/cs/program.cs" id="Snippet0":::
+
]]>
@@ -215,13 +215,13 @@
The status of the asynchronous operation.
Completes an asynchronous operation that notifies workflow instance completion associated with this .
- method. Notice that the base class method is called.
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/wfcreationcontext/cs/program.cs" id="Snippet2":::
-
+ method. Notice that the base class method is called.
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/wfcreationcontext/cs/program.cs" id="Snippet2":::
+
]]>
diff --git a/xml/System.ServiceModel.Activities/WorkflowHostingEndpoint.xml b/xml/System.ServiceModel.Activities/WorkflowHostingEndpoint.xml
index 99625bb200e..412dac59411 100644
--- a/xml/System.ServiceModel.Activities/WorkflowHostingEndpoint.xml
+++ b/xml/System.ServiceModel.Activities/WorkflowHostingEndpoint.xml
@@ -16,13 +16,13 @@
An abstract implementation of . Derive from this class to expose contracts that support workflow creation and bookmark resumption.
- class.
-
- :::code language="csharp" source="~/snippets/csharp/System.ServiceModel.Activities/WorkflowHostingEndpoint/Overview/CreationEndpoint.cs" id="Snippet2":::
-
+ class.
+
+ :::code language="csharp" source="~/snippets/csharp/System.ServiceModel.Activities/WorkflowHostingEndpoint/Overview/CreationEndpoint.cs" id="Snippet2":::
+
]]>
@@ -113,11 +113,11 @@
Gets a collection of instances .
A collection of correlation queries.
- .
-
+ .
+
]]>
@@ -151,13 +151,13 @@
Override to create a new instance.
A workflow creation context object.
- method.
-
-
-
+ method.
+
+
+
]]>
@@ -187,18 +187,18 @@
Override to return the instance ID for the workflow instance being created.
The instance ID for the newly created workflow instance.
- method.
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/creationendpoint/cs/creationendpoint.cs" id="Snippet0":::
-
+ method.
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/creationendpoint/cs/creationendpoint.cs" id="Snippet0":::
+
]]>
@@ -232,13 +232,13 @@
Override to return a bookmark to be resumed on the workflow instance.
A bookmark.
- method.
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/resumebookmarkendpoint/cs/resumebookmarkendpoint.cs" id="Snippet0":::
-
+ method.
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/resumebookmarkendpoint/cs/resumebookmarkendpoint.cs" id="Snippet0":::
+
]]>
diff --git a/xml/System.ServiceModel.Activities/WorkflowServiceHost.xml b/xml/System.ServiceModel.Activities/WorkflowServiceHost.xml
index e9442d1ace9..30491de908e 100644
--- a/xml/System.ServiceModel.Activities/WorkflowServiceHost.xml
+++ b/xml/System.ServiceModel.Activities/WorkflowServiceHost.xml
@@ -16,13 +16,13 @@
Provides a host for workflows. Supports features like messaging activities, multi-instancing, and configuration.
- class.
-
- :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/sendreceiveparameters/cs/echoworkflowservice/program.cs" id="Snippet03":::
-
+ class.
+
+ :::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/sendreceiveparameters/cs/echoworkflowservice/program.cs" id="Snippet03":::
+
]]>
@@ -81,12 +81,12 @@
An array of base addresses for the workflow service.
Initializes a new instance of the class using the specified activity and base addresses.
-
@@ -209,12 +209,12 @@
The service endpoint to add.
Adds a service endpoint to the workflow service host.
- method.
-
-
+ method.
+
+
]]>
@@ -246,12 +246,12 @@
Adds a service endpoint to the workflow service host using the specified contract, binding, and address.
A service endpoint.
-
@@ -283,12 +283,12 @@
Adds a service endpoint to the workflow service host using the specified contract, binding, and address.
A service endpoint.
-
@@ -322,12 +322,12 @@
Adds a service endpoint to the workflow service host using the specified contract, binding, endpoint address, and listen URI.
A service endpoint.
-
@@ -361,12 +361,12 @@
Adds a service endpoint to the workflow service host using the specified contract, binding, endpoint address, and listen URI.
A service endpoint.
-
@@ -401,12 +401,12 @@
Adds a service endpoint to the workflow service host using the specified contract, binding, endpoint address, listen URI, and behavior configuration name.
A service endpoint.
-
@@ -441,12 +441,12 @@
Adds a service endpoint to the workflow service host using the specified implemented contract, binding, endpoint address, listen URI, and a behavior configuration name.
A service endpoint.
-
@@ -474,11 +474,11 @@
Creates a service description of the hosted workflow service using the specified key/value pair collection of address, binding, contract and behavior service endpoint information.
A service for the hosted workflow service.
-
@@ -626,11 +626,11 @@
The period of time the close operation has to complete before timing out.
Closes down the hosted service, including the channel dispatchers and associated instance contexts and listeners.
- is called, but persistence is not guaranteed in this scenario. If important business data is being hosted, the instances should persist frequently (such as after each Send operation, or after an interval of time) to ensure that data is not lost.
-
+ is called, but persistence is not guaranteed in this scenario. If important business data is being hosted, the instances should persist frequently (such as after each Send operation, or after an interval of time) to ensure that data is not lost.
+
]]>
@@ -753,12 +753,12 @@
Gets a object to add or remove extensions to the workflow service instance.
workflow instance extension manager.
-
diff --git a/xml/System.ServiceModel.Channels/AddressHeader.xml b/xml/System.ServiceModel.Channels/AddressHeader.xml
index 8cf2e18621d..986d3fc9e91 100644
--- a/xml/System.ServiceModel.Channels/AddressHeader.xml
+++ b/xml/System.ServiceModel.Channels/AddressHeader.xml
@@ -102,7 +102,7 @@
to create new objects.
+ Use the to create new objects.
]]>
@@ -469,7 +469,7 @@
## Remarks
This is the string-based implementation.
- is suitable for use in hashing algorithms and data structures like a hash table.
+ is suitable for use in hashing algorithms and data structures like a hash table.
@@ -494,7 +494,7 @@
overload if you want to use a customized XML formatter; otherwise use the overload.
+ Use the overload if you want to use a customized XML formatter; otherwise use the overload.
]]>
@@ -542,7 +542,7 @@
## Remarks
When using this overload, you must supply a type for the generic parameter `T`. The type of the return value is determined by the generic type parameter.
- Use the overload if you want to use a customized XML formatter.
+ Use the overload if you want to use a customized XML formatter.
@@ -603,7 +603,7 @@
## Remarks
When using this overload, you must supply a type for the generic parameter `T`. The type of the return value is determined by the generic type parameter.
- Use this overload only if you want to use a customized XML formatter; otherwise use the overload.
+ Use this overload only if you want to use a customized XML formatter; otherwise use the overload.
@@ -839,7 +839,7 @@
and overloads provide interfaces to use in writing an address header to a stream or file. Both call the abstract method, so users must provide an implementation of this method to use these overloads.
+ The and overloads provide interfaces to use in writing an address header to a stream or file. Both call the abstract method, so users must provide an implementation of this method to use these overloads.
]]>
@@ -885,7 +885,7 @@
## Remarks
This overload calls the abstract
- method, so users must provide an implementation of that method to use this method.
+ method, so users must provide an implementation of that method to use this method.
@@ -939,7 +939,7 @@
## Remarks
This overload wraps as a and then the calls the abstract
- method. Users must provide an implementation for that abstract method to use this overload.
+ method. Users must provide an implementation for that abstract method to use this overload.
diff --git a/xml/System.ServiceModel.Channels/AddressHeaderCollection.xml b/xml/System.ServiceModel.Channels/AddressHeaderCollection.xml
index 7bbd338386f..b764cf67cf4 100644
--- a/xml/System.ServiceModel.Channels/AddressHeaderCollection.xml
+++ b/xml/System.ServiceModel.Channels/AddressHeaderCollection.xml
@@ -52,7 +52,7 @@
can be initialized with an set of objects and then searched for a header with a specific qualified name using the method. To find all of the headers with a specific qualified name, use the method. The method is used to add headers to the headers of a specified message.
+ The can be initialized with an set of objects and then searched for a header with a specific qualified name using the method. To find all of the headers with a specific qualified name, use the method. The method is used to add headers to the headers of a specified message.
]]>
@@ -292,7 +292,7 @@
method instead.
+ If you need to find all the address headers in the collection with the specified name and namespace, use the method instead.
is not the ideal exception type when there is more than one header in the collection. Callers of this method should take care to handle this exception when the collection contains multiple entries with the same name and namespace.
diff --git a/xml/System.ServiceModel.Channels/AsymmetricSecurityBindingElement.xml b/xml/System.ServiceModel.Channels/AsymmetricSecurityBindingElement.xml
index 0631295cf1b..3fb111ed17d 100644
--- a/xml/System.ServiceModel.Channels/AsymmetricSecurityBindingElement.xml
+++ b/xml/System.ServiceModel.Channels/AsymmetricSecurityBindingElement.xml
@@ -32,7 +32,7 @@
2. Create custom binding elements that is above this binding element in the binding stack, such as the optional and .
-3. Add the created elements in the preceding order to the using the method.
+3. Add the created elements in the preceding order to the using the method.
4. Create an instance of and add it to the collection.
@@ -625,7 +625,7 @@
## Remarks
This method writes binding-related statements into the WSDL information exposed by a particular contract and is used by Windows Communication Foundation (WCF) to communicate to clients the existence of this custom binding element in the binding stack.
- This method takes two parameters: the and objects. Use the , , and methods to obtain collections of policy assertions that have already been exported at various scopes. Then use this method to add your own policy assertions to the appropriate collection.
+ This method takes two parameters: the and objects. Use the , , and methods to obtain collections of policy assertions that have already been exported at various scopes. Then use this method to add your own policy assertions to the appropriate collection.
The property exposes the for the endpoint that is being exported. This allows this method 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.
@@ -659,7 +659,7 @@
includes the , , , and values of the current instance.
+ Information returned by includes the , , , and values of the current instance.
]]>
diff --git a/xml/System.ServiceModel.Channels/Binding.xml b/xml/System.ServiceModel.Channels/Binding.xml
index 64fafba94dc..fb31f2cd21b 100644
--- a/xml/System.ServiceModel.Channels/Binding.xml
+++ b/xml/System.ServiceModel.Channels/Binding.xml
@@ -80,7 +80,7 @@
||1 minute|
||10 minutes|
- When you create a binding by inheriting from , you must override .
+ When you create a binding by inheriting from , you must override .
In addition, you can define your own binding elements and insert them between any of the defined layers in the preceding table. For more information, see the class.
@@ -687,7 +687,7 @@
and catch the exception generated if it cannot be built.
+ Use this method if you want to check that the channel factory for channels of type `TChannel` can be build for the `context` provided before attempting to actually build the factory. Alternatively, try to build the channel factory by calling and catch the exception generated if it cannot be built.
]]>
@@ -744,7 +744,7 @@
and catch the exception generated if it cannot be built.
+ Use this method if you want to check that the channel factory for channels of type `TChannel` can be build for the binding `parameters` specified before attempting to actually build the factory. Alternatively, try to build the channel factory by calling and catch the exception generated if it cannot be built.
]]>
@@ -794,7 +794,7 @@
and catch the exception generated if it cannot be built.
+ Use this method if you want to check that the channel factory for channels of type `TChannel` can be build for the binding `parameters` specified before attempting to actually build the factory. Alternatively, try to build the channel factory by calling and catch the exception generated if it cannot be built.
]]>
@@ -856,7 +856,7 @@
and catch the exception generated if it cannot be built.
+ Use this method if you want to check that the channel listener for channels of type `TChannel` can be build for the binding `parameters` specified before attempting to actually build the listener. Alternatively, try to build the channel listener by calling and catch the exception generated if it cannot be built.
]]>
@@ -902,7 +902,7 @@
and catch the exception generated if it cannot be built.
+ Use this method if you want to check that the channel listener for channels of type `TChannel` can be build for the binding `parameters` specified before attempting to actually build the listener. Alternatively, try to build the channel listener by calling and catch the exception generated if it cannot be built.
]]>
diff --git a/xml/System.ServiceModel.Channels/BindingContext.xml b/xml/System.ServiceModel.Channels/BindingContext.xml
index 57281233ee4..7db9e731b85 100644
--- a/xml/System.ServiceModel.Channels/BindingContext.xml
+++ b/xml/System.ServiceModel.Channels/BindingContext.xml
@@ -535,7 +535,7 @@
on the next binding element stored in the binding context.
+ Clones the binding context and calls on the next binding element stored in the binding context.
diff --git a/xml/System.ServiceModel.Channels/BindingElement.xml b/xml/System.ServiceModel.Channels/BindingElement.xml
index 1b30147b9b3..e84ba24b9e4 100644
--- a/xml/System.ServiceModel.Channels/BindingElement.xml
+++ b/xml/System.ServiceModel.Channels/BindingElement.xml
@@ -60,7 +60,7 @@
Similarly, on the receiving side a binding is used to build a , which listens for incoming messages. The provides messages to the listening application by creating channel stacks and handing the application a reference to the top channel. The application then uses this channel to receive incoming messages.
> [!NOTE]
-> If you are adding message headers that must be encrypted you must return a instance with your requirements from the method when asked for .
+> If you are adding message headers that must be encrypted you must return a instance with your requirements from the method when asked for .
@@ -302,7 +302,7 @@
and catch the exception generated if it cannot be built.
+ Use this method if you want to check that the channel factory for channels of type `TChannel` can be build for the `context` provided before attempting to build the factory. Alternatively, build the channel factory by calling and catch the exception generated if it cannot be built.
@@ -355,7 +355,7 @@
and catch the exception generated if it cannot be built.
+ Use this method if you want to check that the channel listener for channels of type `TChannel` can be build for the `context` provided before attempting to build the listener. Alternatively, build the channel listener by calling and catch the exception generated if it cannot be built.
@@ -404,7 +404,7 @@
method to return a deep clone of your binding element. Returning a clone enables the runtime to support the case in which multiple custom bindings share a custom binding element. If a clone is not returned, the run-time behavior is undefined.
+ Implement the method to return a deep clone of your binding element. Returning a clone enables the runtime to support the case in which multiple custom bindings share a custom binding element. If a clone is not returned, the run-time behavior is undefined.
A deep clone of an object creates a copy of the object and a copy of everything directly or indirectly referenced by that object. (This is also called copying the entire object graph.) A shallow clone of an object, by contrast, is a copy of the object only. If the object contains references to other objects, the shallow copy does not create copies of the referred objects; instead, it copies only the references to the original objects.
diff --git a/xml/System.ServiceModel.Channels/BodyWriter.xml b/xml/System.ServiceModel.Channels/BodyWriter.xml
index d3dcdbd035f..7d3f3b2666a 100644
--- a/xml/System.ServiceModel.Channels/BodyWriter.xml
+++ b/xml/System.ServiceModel.Channels/BodyWriter.xml
@@ -46,19 +46,19 @@
Represents the writer of the message body.
- to the . A message calls the class derived from whenever it requires the body to be written using an .
-
-
-
-## Examples
- The following example shows how to derive a class from . This override takes in an array of strings and writes them to a .
-
+ to the . A message calls the class derived from whenever it requires the body to be written using an .
+
+
+
+## Examples
+ The following example shows how to derive a class from . This override takes in an array of strings and writes them to a .
+
:::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/s_uebodywriter/cs/program.cs" id="Snippet1":::
- :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_CFX/s_uebodywriter/vb/module1.vb" id="Snippet1":::
-
+ :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_CFX/s_uebodywriter/vb/module1.vb" id="Snippet1":::
+
]]>
@@ -96,11 +96,11 @@
if the body writer can be called multiple times; otherwise .
Initializes a new instance of the class that explicitly indicates whether to buffer.
-
@@ -178,19 +178,19 @@
Creates a buffered copy of the body.
A that contains a copy of this object.
- is `true` then the object is returned. If is `false` then the contents of the up to `maxBufferSize` is returned. This also calls as an extensibility point.
-
-
-
-## Examples
- The following sample shows how to create a buffered copy of an existing instance.
-
+ is `true` then the object is returned. If is `false` then the contents of the up to `maxBufferSize` is returned. This also calls as an extensibility point.
+
+
+
+## Examples
+ The following sample shows how to create a buffered copy of an existing instance.
+
:::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/s_uebodywriter/cs/snippets.cs" id="Snippet2":::
- :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_CFX/s_uebodywriter/vb/snippets.vb" id="Snippet2":::
-
+ :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_CFX/s_uebodywriter/vb/snippets.vb" id="Snippet2":::
+
]]>
The is less than zero.
@@ -268,11 +268,11 @@
if the body writer can be called multiple times; otherwise .
-
@@ -350,13 +350,13 @@
Provides an extensibility point when the body contents are written.
The with the specified maximum buffer size.
- can override this method to create a buffered copy of the . But the default implementation of calls , so overriding just should be easier and work for most scenarios.
-
- Note that the returned must be buffered, that is must be `true`.
-
+ can override this method to create a buffered copy of the . But the default implementation of calls , so overriding just should be easier and work for most scenarios.
+
+ Note that the returned must be buffered, that is must be `true`.
+
]]>
@@ -428,19 +428,19 @@
The used to write out the message body.
When implemented, provides an extensibility point when the body contents are written.
- . This is the key method that writes the body. If the is buffered then this method is called only once.
-
-
-
-## Examples
- The following example illustrates an override of the method.
-
+ . This is the key method that writes the body. If the is buffered then this method is called only once.
+
+
+
+## Examples
+ The following example illustrates an override of the method.
+
:::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/s_uebodywriter/cs/program.cs" id="Snippet3":::
- :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_CFX/s_uebodywriter/vb/module1.vb" id="Snippet3":::
-
+ :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_CFX/s_uebodywriter/vb/module1.vb" id="Snippet3":::
+
]]>
@@ -480,19 +480,19 @@
The used to write out the message body.
Writes out the contents of the message body.
- calls , so overriding provides the best point of extension.
-
-
-
-## Examples
- The following sample shows how to call the method.
-
+ calls , so overriding provides the best point of extension.
+
+
+
+## Examples
+ The following sample shows how to call the method.
+
:::code language="csharp" source="~/snippets/csharp/VS_Snippets_CFX/s_uebodywriter/cs/program.cs" id="Snippet4":::
- :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_CFX/s_uebodywriter/vb/module1.vb" id="Snippet4":::
-
+ :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_CFX/s_uebodywriter/vb/module1.vb" id="Snippet4":::
+
]]>
diff --git a/xml/System.ServiceModel.Channels/ChannelBase.xml b/xml/System.ServiceModel.Channels/ChannelBase.xml
index 220019eab38..6ba4a89192b 100644
--- a/xml/System.ServiceModel.Channels/ChannelBase.xml
+++ b/xml/System.ServiceModel.Channels/ChannelBase.xml
@@ -56,24 +56,24 @@
Provides the base implementation for custom channels.
- class provides an abstract base class implementation of the interface. It also requires that each channel be associated with a channel manager. Note that the only constructor available for creating instances of requires a `channelManager` input parameter.
-
- State changes are managed by inheriting from the implementation of the state machine.
-
- The gets its default communication timeouts for the open, close, send and receive operations from the associated with it.
-
- The also manages the manager for you. In addition to exposing a reference to the manager, the base class also notifies the manager when channels are created and destroyed. But the reference to the manager is only good until the channel is destroyed.
-
- Even if you do use the base class, you must still provide behaviors for opening and closing the channel. The default implementations of these methods do not provide useful information.
-
- You must also make sure to override whenever you implement a channel. is an excellent way to communicate information along the channel stack without having to know what channels are below you, or what channels above you may perform queries. Define interfaces that can be queried for available information. Whenever you do not recognize the type argument for , delegate down to the next channel in the stack or return `null` if you are creating a new transport channel at the bottom of the stack.
-
+ The class provides an abstract base class implementation of the interface. It also requires that each channel be associated with a channel manager. Note that the only constructor available for creating instances of requires a `channelManager` input parameter.
+
+ State changes are managed by inheriting from the implementation of the state machine.
+
+ The gets its default communication timeouts for the open, close, send and receive operations from the associated with it.
+
+ The also manages the manager for you. In addition to exposing a reference to the manager, the base class also notifies the manager when channels are created and destroyed. But the reference to the manager is only good until the channel is destroyed.
+
+ Even if you do use the base class, you must still provide behaviors for opening and closing the channel. The default implementations of these methods do not provide useful information.
+
+ You must also make sure to override whenever you implement a channel. is an excellent way to communicate information along the channel stack without having to know what channels are below you, or what channels above you may perform queries. Define interfaces that can be queried for available information. Whenever you do not recognize the type argument for , delegate down to the next channel in the stack or return `null` if you are creating a new transport channel at the bottom of the stack.
+
]]>
@@ -110,11 +110,11 @@
The that provides default timeouts for the channel operations (send, receive, open, and close).
Initializes a new instance of the class.
- requires a `channelManager` input parameter.
-
+ requires a `channelManager` input parameter.
+
]]>
@@ -153,13 +153,13 @@
Gets the default interval of time provided for a close operation to complete.
The default that specifies how long the close operation has to complete before timing out.
- associated with for the channel.
-
- All operations that are potentially lengthy must have a timeout. Methods that do not take explicit timeouts, must delegate to those methods with default timeouts or must not do any work that blocks. Timeouts are the total limit for high-level operations for which they are to complete, so any retries must be limited to the time not already accessed by earlier tries.
-
+ associated with for the channel.
+
+ All operations that are potentially lengthy must have a timeout. Methods that do not take explicit timeouts, must delegate to those methods with default timeouts or must not do any work that blocks. Timeouts are the total limit for high-level operations for which they are to complete, so any retries must be limited to the time not already accessed by earlier tries.
+
]]>
@@ -196,13 +196,13 @@
Gets the default interval of time provided for an open operation to complete.
The default that specifies how long the open operation has to complete before timing out.
- associated with for the channel.
-
- All operations that are potentially lengthy must have a timeout. Methods that do not take explicit timeouts, must delegate to those methods with default timeouts or must not do any work that blocks. Timeouts are the total limit for high-level operations for which they are to complete, so any retries must be limited to the time not already accessed by earlier tries.
-
+ associated with for the channel.
+
+ All operations that are potentially lengthy must have a timeout. Methods that do not take explicit timeouts, must delegate to those methods with default timeouts or must not do any work that blocks. Timeouts are the total limit for high-level operations for which they are to complete, so any retries must be limited to the time not already accessed by earlier tries.
+
]]>
@@ -239,13 +239,13 @@
Gets the default interval of time provided for a receive operation to complete.
The default that specifies how long the receive operation has to complete before timing out.
- associated with for the channel.
-
- All operations that are potentially lengthy must have a timeout. Methods that do not take explicit timeouts, must delegate to those methods with default timeouts or must not do any work that blocks. Timeouts are the total limit for high-level operations for which they are to complete, so any retries must be limited to the time not already accessed by earlier tries.
-
+ associated with for the channel.
+
+ All operations that are potentially lengthy must have a timeout. Methods that do not take explicit timeouts, must delegate to those methods with default timeouts or must not do any work that blocks. Timeouts are the total limit for high-level operations for which they are to complete, so any retries must be limited to the time not already accessed by earlier tries.
+
]]>
@@ -282,13 +282,13 @@
Gets the default interval of time provided for a send operation to complete.
The default that specifies how long the send operation has to complete before timing out.
- associated with for the channel.
-
- All operations that are potentially lengthy must have a timeout. Methods that do not take explicit timeouts, must delegate to those methods with default timeouts or must not do any work that blocks. Timeouts are the total limit for high-level operations for which they are to complete, so any retries must be limited to the time not already accessed by earlier tries.
-
+ associated with for the channel.
+
+ All operations that are potentially lengthy must have a timeout. Methods that do not take explicit timeouts, must delegate to those methods with default timeouts or must not do any work that blocks. Timeouts are the total limit for high-level operations for which they are to complete, so any retries must be limited to the time not already accessed by earlier tries.
+
]]>
@@ -337,13 +337,13 @@
Returns the typed object requested, if present, from the appropriate layer in the channel stack.
The typed object requested, if it is present, or , if it is not.
- whenever you implement a channel. is an excellent way to communicate information along the channel stack without having to know what channels are below you, or what channels above you may perform queries. Define interfaces that can be queried for available information. Whenever you do not recognize the type argument for , delegate down to the next channel in the stack or return `null` if you are creating a new transport channel at the bottom of the stack.
-
+ whenever you implement a channel. is an excellent way to communicate information along the channel stack without having to know what channels are below you, or what channels above you may perform queries. Define interfaces that can be queried for available information. Whenever you do not recognize the type argument for , delegate down to the next channel in the stack or return `null` if you are creating a new transport channel at the bottom of the stack.
+
]]>
@@ -386,11 +386,11 @@
Gets the channel manager that is associated with the current channel.
The that is associated with the current channel.
- must have a associated with it.
-
+ must have a associated with it.
+
]]>
@@ -427,11 +427,11 @@
Uses diagnostic tracing during the transition into the closing state.
-
@@ -471,11 +471,11 @@
Gets the interval of time after which the close method, invoked by a communication object, times out.
The that specifies the interval of time to wait for the close method to time out.
- calls .
-
+ calls .
+
]]>
@@ -515,11 +515,11 @@
Gets the interval of time after which the open method, invoked by a communication object, times out.
The that specifies the interval of time to wait for the open method to time out.
- calls .
-
+ calls .
+
]]>
@@ -565,11 +565,11 @@
Gets the interval of time after which the receive method, invoked by a communication object, times out.
The that specifies the interval of time to wait for the receive method to time out.
- calls .
-
+ calls .
+
]]>
@@ -615,11 +615,11 @@
Gets the interval of time after which the send method, invoked by a communication object, times out.
The that specifies the interval of time to wait for the send method to time out.
- calls .
-
+ calls .
+
]]>
diff --git a/xml/System.ServiceModel.Channels/ChannelFactoryBase.xml b/xml/System.ServiceModel.Channels/ChannelFactoryBase.xml
index 109dc368e82..18a0c799e72 100644
--- a/xml/System.ServiceModel.Channels/ChannelFactoryBase.xml
+++ b/xml/System.ServiceModel.Channels/ChannelFactoryBase.xml
@@ -78,7 +78,7 @@
constructor initializes timeout properties with the service model timeout values when exchanging messages. The default value is 1 minute for open, send, and close operations and 10 minutes for the receive operation. Use if you want to specify other values for these operation timeouts.
+ The default constructor initializes timeout properties with the service model timeout values when exchanging messages. The default value is 1 minute for open, send, and close operations and 10 minutes for the receive operation. Use if you want to specify other values for these operation timeouts.
]]>
@@ -115,7 +115,7 @@
if you want to specify other values for these operation timeouts.
+ The parameterless constructor initializes timeout properties with the service model timeout values when exchanging messages. The default value is 1 minute for open, send, and close operations and 10 minutes for the receive operation. Use if you want to specify other values for these operation timeouts.
]]>
@@ -156,7 +156,7 @@
instead of the parameterless constructor if you want to specify custom values for the open, send, receive, and close operation timeouts instead of using the service model default values.
+ Use instead of the parameterless constructor if you want to specify custom values for the open, send, receive, and close operation timeouts instead of using the service model default values.
]]>
@@ -203,7 +203,7 @@
object. The default constructor sets the property to a value of 1 minute. Use if you want to specify another value for this timeout.
+ This value is set when creating a new object. The default constructor sets the property to a value of 1 minute. Use if you want to specify another value for this timeout.
]]>
@@ -250,7 +250,7 @@
object. The default constructor sets the property to a value of 1 minute. Use if you want to specify another value for this timeout.
+ This value is set when creating a new object. The default constructor sets the property to a value of 1 minute. Use if you want to specify another value for this timeout.
]]>
@@ -297,7 +297,7 @@
object. The default constructor sets the property to a value of 10 minutes. Use if you want to specify another value for this timeout.
+ This value is set when creating a new object. The default constructor sets the property to a value of 10 minutes. Use if you want to specify another value for this timeout.
]]>
@@ -344,7 +344,7 @@
object. The default constructor sets the property to a value of 1 minute. Use if you want to specify another value for this timeout.
+ This value is set when creating a new object. The default constructor sets the property to a value of 1 minute. Use if you want to specify another value for this timeout.
]]>
diff --git a/xml/System.ServiceModel.Channels/ChannelFactoryBase`1.xml b/xml/System.ServiceModel.Channels/ChannelFactoryBase`1.xml
index 9831199803a..a648b4a1255 100644
--- a/xml/System.ServiceModel.Channels/ChannelFactoryBase`1.xml
+++ b/xml/System.ServiceModel.Channels/ChannelFactoryBase`1.xml
@@ -61,13 +61,13 @@
The type of channel the factory produces.
Provides a common base implementation for channel factories on the client to create channels of a specified type connected to a specified address.
- uses the specified address as the destination for outgoing messages. The ServiceAddress.Uri property is used as the To header in the message. The ServiceReference.Via property is used as the physical destination to send messages to. This is typically the same as the ServiceAddress.Uri value.
-
+ uses the specified address as the destination for outgoing messages. The ServiceAddress.Uri property is used as the To header in the message. The ServiceReference.Via property is used as the physical destination to send messages to. This is typically the same as the ServiceAddress.Uri value.
+
]]>
@@ -81,11 +81,11 @@
Initializes a new instance of the class.
- constructor initializes timeout properties with the service model timeout values when exchanging messages. The default value is 1 minute for open, send, and close operations and 10 minutes for the receive operation. Use if you want to specify other values for these operation timeouts.
-
+ constructor initializes timeout properties with the service model timeout values when exchanging messages. The default value is 1 minute for open, send, and close operations and 10 minutes for the receive operation. Use if you want to specify other values for these operation timeouts.
+
]]>
@@ -124,11 +124,11 @@
Initializes a new instance of the class.
- if you want to specify other values for these operation timeouts.
-
+ if you want to specify other values for these operation timeouts.
+
]]>
@@ -165,11 +165,11 @@
The that specifies the default timeouts for open, send, receive, and close operations when exchanging messages.
Initializes a new instance of the class with the default communication timeouts specified.
- instead of the parameterless constructor if you want to specify custom values for the open, send, receive, and close operation timeouts instead of using the service model default values.
-
+ instead of the parameterless constructor if you want to specify custom values for the open, send, receive, and close operation timeouts instead of using the service model default values.
+
]]>
@@ -223,13 +223,13 @@
Creates a particular type of channel with a specified endpoint address.
A channel of type with the specified .
- when invoked. This method cannot be overridden by a derived class.
-
- This uses as the transport address to which messages are sent on the output channel.
-
+ when invoked. This method cannot be overridden by a derived class.
+
+ This uses as the transport address to which messages are sent on the output channel.
+
]]>
@@ -277,11 +277,11 @@
Creates a particular type of channel with specified transport and endpoint addresses.
A channel of type with the specified remote and transport addresses.
- when invoked.
-
+ when invoked.
+
]]>
@@ -318,11 +318,11 @@
Aborts each channel managed by the channel factory.
- .
-
+ .
+
]]>
@@ -404,13 +404,13 @@
The that specifies how long the on-close operation has to complete before timing out.
Closes all the channels associated with the channel factory within a specified interval of time.
- .
-
+ .
+
]]>
@@ -453,11 +453,11 @@
When implemented in a derived class, provides an extensibility point when creating channels.
A channel of type with the specified addresses.
- when invoked.
-
+ when invoked.
+
]]>
@@ -531,11 +531,11 @@
Confirms that the channel factory is opened and ready to create channels.
-
The communication object is in a or state.
diff --git a/xml/System.ServiceModel.Channels/ChannelListenerBase.xml b/xml/System.ServiceModel.Channels/ChannelListenerBase.xml
index 6768c48b6e1..d99055b024d 100644
--- a/xml/System.ServiceModel.Channels/ChannelListenerBase.xml
+++ b/xml/System.ServiceModel.Channels/ChannelListenerBase.xml
@@ -44,7 +44,7 @@
constructor initializes timeout properties with the service model timeout values when exchanging messages. The default value is 1 minute for open, send, and close operations and 10 minutes for the receive operation. Use if you want to specify other values for these operation timeouts.
+ The default constructor initializes timeout properties with the service model timeout values when exchanging messages. The default value is 1 minute for open, send, and close operations and 10 minutes for the receive operation. Use if you want to specify other values for these operation timeouts.
]]>
@@ -69,7 +69,7 @@
if you want to specify other values for these operation timeouts.
+ The parameterless constructor initializes timeout properties with the service model timeout values when exchanging messages. The default value is 1 minute for open, send, and close operations and 10 minutes for the receive operation. Use if you want to specify other values for these operation timeouts.
]]>
@@ -98,7 +98,7 @@
instead of the parameterless constructor if you want to specify custom values for the open, send, receive, and close operation timeouts instead of using the service model default values.
+ Use instead of the parameterless constructor if you want to specify custom values for the open, send, receive, and close operation timeouts instead of using the service model default values.
]]>
@@ -167,7 +167,7 @@
object. The default constructor sets the property to a value of 1 minute. Use if you want to specify another value for this timeout.
+ This value is set when creating a new object. The default constructor sets the property to a value of 1 minute. Use if you want to specify another value for this timeout.
]]>
@@ -202,7 +202,7 @@
object. The default constructor sets the property to a value of 1 minute. Use if you want to specify another value for this timeout.
+ This value is set when creating a new object. The default constructor sets the property to a value of 1 minute. Use if you want to specify another value for this timeout.
]]>
@@ -237,7 +237,7 @@
object. The default constructor sets the property to a value of 10 minutes. Use if you want to specify another value for this timeout.
+ This value is set when creating a new object. The default constructor sets the property to a value of 10 minutes. Use if you want to specify another value for this timeout.
]]>
@@ -272,7 +272,7 @@
object. The default constructor sets the property to a value of 1 minute. Use if you want to specify another value for this timeout.
+ This value is set when creating a new object. The default constructor sets the property to a value of 1 minute. Use if you want to specify another value for this timeout.
]]>
diff --git a/xml/System.ServiceModel.Channels/ChannelListenerBase`1.xml b/xml/System.ServiceModel.Channels/ChannelListenerBase`1.xml
index 51e12a0c578..81adef3bd68 100644
--- a/xml/System.ServiceModel.Channels/ChannelListenerBase`1.xml
+++ b/xml/System.ServiceModel.Channels/ChannelListenerBase`1.xml
@@ -36,11 +36,11 @@
The type of channel the channel listeners accept.
Provides a common base implementation for channel listeners on a service to accept channels produced by the client factories.
-
@@ -53,11 +53,11 @@
Initializes a new instance of the class.
- constructor initializes timeout properties with the service model timeout values when exchanging messages. The default value is 1 minute for open, send, and close operations and 10 minutes for the receive operation. Use if you want to specify other values for these operation timeouts.
-
+ constructor initializes timeout properties with the service model timeout values when exchanging messages. The default value is 1 minute for open, send, and close operations and 10 minutes for the receive operation. Use if you want to specify other values for these operation timeouts.
+
]]>
@@ -84,11 +84,11 @@
Initializes a new instance of the class.
- if you want to specify other values for these operation timeouts.
-
+ if you want to specify other values for these operation timeouts.
+
]]>
@@ -119,11 +119,11 @@
The that specify the default timeouts for open, send, receive, and close operations when exchanging messages.
Initializes a new instance of the class with specified default communication timeouts.
- instead of the parameterless constructor if you want to specify custom values for the open, send, receive, and close operation timeouts instead of using the service model default values.
-
+ instead of the parameterless constructor if you want to specify custom values for the open, send, receive, and close operation timeouts instead of using the service model default values.
+
]]>
diff --git a/xml/System.ServiceModel.Channels/ChannelManagerBase.xml b/xml/System.ServiceModel.Channels/ChannelManagerBase.xml
index 593687e9da5..22472774cb8 100644
--- a/xml/System.ServiceModel.Channels/ChannelManagerBase.xml
+++ b/xml/System.ServiceModel.Channels/ChannelManagerBase.xml
@@ -50,15 +50,15 @@
Provides a base implementation for managing the default timeouts that are associated with channel and listener factories.
- and channel manager classes for managing the default timeouts that are associated with the channel factories and listeners. Channels are added to the list maintained by the manager by using one of the methods. Abstract properties for send and receive timeouts used by the channels and listeners that are produced are specified to coordinate the values set for the derived channel and listener factories.
-
- The , which provides the base implementation for custom channels, gets its default communication timeouts for the open, close, send and receive operations from the associated with it.
-
- The also takes care of managing the manager for you. In addition to exposing a reference to the manager, the base class also notifies the manager when channels are created and destroyed. But the reference to the manager is only good until the channel is destroyed.
-
+ and channel manager classes for managing the default timeouts that are associated with the channel factories and listeners. Channels are added to the list maintained by the manager by using one of the methods. Abstract properties for send and receive timeouts used by the channels and listeners that are produced are specified to coordinate the values set for the derived channel and listener factories.
+
+ The , which provides the base implementation for custom channels, gets its default communication timeouts for the open, close, send and receive operations from the associated with it.
+
+ The also takes care of managing the manager for you. In addition to exposing a reference to the manager, the base class also notifies the manager when channels are created and destroyed. But the reference to the manager is only good until the channel is destroyed.
+
]]>
@@ -131,11 +131,11 @@
When overridden in a derived class, gets the default interval of time a channel has to complete the reception of a message.
The default that specifies how long the channel has to complete the reception of a message before timing out once the receive method has been invoked.
-
@@ -172,11 +172,11 @@
When overridden in a derived class, gets the default interval of time a channel has to complete the sending of a message.
The default that specifies how long the channel has to complete the sending of a message before timing out once the send method has been invoked.
-
@@ -216,11 +216,11 @@
Gets the interval of time after which the close method, invoked by a communication object, times out.
The that specifies the interval of time to wait for the close method to time out.
-
@@ -260,11 +260,11 @@
Gets the interval of time after which the open method, invoked by a communication object, times out.
The that specifies the interval of time to wait for the open method to time out.
-
@@ -310,11 +310,11 @@
Gets the interval of time after which the receive method, invoked by a communication object, times out.
The that specifies the interval of time to wait for the receive method to time out.
- calls .
-
+ calls .
+
]]>
@@ -360,11 +360,11 @@
Gets the interval of time after which the send method, invoked by a communication object, times out.
The that specifies the interval of time to wait for the send method to time out.
- calls .
-
+ calls .
+
]]>
diff --git a/xml/System.ServiceModel.Channels/ChannelParameterCollection.xml b/xml/System.ServiceModel.Channels/ChannelParameterCollection.xml
index a4697d81f7b..b1f842f97b9 100644
--- a/xml/System.ServiceModel.Channels/ChannelParameterCollection.xml
+++ b/xml/System.ServiceModel.Channels/ChannelParameterCollection.xml
@@ -49,11 +49,11 @@
Represents a collection of channel parameters.
-
@@ -67,11 +67,11 @@
Initializes a new instance of the class.
- to `channel` by calling , or simply invoke the parent constructor by calling .
-
+ to `channel` by calling , or simply invoke the parent constructor by calling .
+
]]>
@@ -110,11 +110,11 @@
Initializes a new instance of the class.
-
@@ -157,11 +157,11 @@
The channel whose parameters are in this collection.
Initializes a new instance of the class.
- set to `channel`.
-
+ set to `channel`.
+
]]>
@@ -204,11 +204,11 @@
Gets the channel whose parameters are in this collection.
The whose parameters are in this collection.
- is called.
-
+ is called.
+
]]>
diff --git a/xml/System.ServiceModel.Channels/CommunicationObject.xml b/xml/System.ServiceModel.Channels/CommunicationObject.xml
index 2f140e40b52..cd5ff7890e6 100644
--- a/xml/System.ServiceModel.Channels/CommunicationObject.xml
+++ b/xml/System.ServiceModel.Channels/CommunicationObject.xml
@@ -50,11 +50,11 @@
Provides a common base implementation for the basic state machine common to all communication-oriented objects in the system, including channels, listeners, and the channel and listener factories.
- class implements the interface for all communication objects in Windows Communication Foundation (WCF). The method implementations handle parameter validation, raise events that notify the occurrence of state transitions, provide the means to associated additional processing with these state transitions, and ensure that such state changes are coordinated.
-
+ class implements the interface for all communication objects in Windows Communication Foundation (WCF). The method implementations handle parameter validation, raise events that notify the occurrence of state transitions, provide the means to associated additional processing with these state transitions, and ensure that such state changes are coordinated.
+
]]>
@@ -168,13 +168,13 @@
Causes a communication object to transition immediately from its current state into the closing state.
- method can be used to cancel any outstanding operations, including outstanding calls to .
-
- To gracefully transition a from any state other than into the state, call or one of its asynchronous versions, .
-
+ method can be used to cancel any outstanding operations, including outstanding calls to .
+
+ To gracefully transition a from any state other than into the state, call or one of its asynchronous versions, .
+
]]>
@@ -230,11 +230,11 @@
Begins an asynchronous operation to close a communication object.
The that references the asynchronous close operation.
- to gracefully transition from any state, other than the state, into the state within a default interval of time. The method allows any unfinished work to be completed before returning. For example, finish sending any buffered messages). This method calls if the communication object was initially in the state.
-
+ to gracefully transition from any state, other than the state, into the state within a default interval of time. The method allows any unfinished work to be completed before returning. For example, finish sending any buffered messages). This method calls if the communication object was initially in the state.
+
]]>
The communication object is not in a or state and cannot be modified.
@@ -286,11 +286,11 @@
Begins an asynchronous operation to close a communication object with a specified timeout.
The that references the asynchronous close operation.
- to gracefully transition from any state, other than the state, into the state with in a specified interval of time. The method allows any unfinished work to be completed before returning. For example, finish sending any buffered messages). This method calls if the communication object was initially in the state.
-
+ to gracefully transition from any state, other than the state, into the state with in a specified interval of time. The method allows any unfinished work to be completed before returning. For example, finish sending any buffered messages). This method calls if the communication object was initially in the state.
+
]]>
The communication object is not in a or state and cannot be modified.
@@ -350,13 +350,13 @@
Begins an asynchronous operation to open a communication object.
The that references the asynchronous open operation.
- method calls and if the communication object is initially in the state.
-
- To insert processing after a communication object transitions to a closing state due to the invocation of a synchronous operation, use the method.
-
+ method calls and if the communication object is initially in the state.
+
+ To insert processing after a communication object transitions to a closing state due to the invocation of a synchronous operation, use the method.
+
]]>
The communication object is not in a or state and cannot be modified.
@@ -408,13 +408,13 @@
Begins an asynchronous operation to open a communication object within a specified interval of time.
The that references the asynchronous open operation.
- method calls and if the communication object is initially in the state.
-
- To insert processing after a communication object transitions to a closing state due to the invocation of a synchronous operation, use the method.
-
+ method calls and if the communication object is initially in the state.
+
+ To insert processing after a communication object transitions to a closing state due to the invocation of a synchronous operation, use the method.
+
]]>
The communication object is not in a or state and cannot be modified.
@@ -468,15 +468,15 @@
Causes a communication object to transition from its current state into the closed state.
- to gracefully transition from any state, other than the state, into the state. The method allows any unfinished work to be completed before returning. For example, finish sending any buffered messages.
-
- The enters the state and remains in it after the method is called until the transition to the state is completed. The transition consists of making successive calls to , , and .
-
- There is also an asynchronous version of the close method that is initiated by calling .
-
+ to gracefully transition from any state, other than the state, into the state. The method allows any unfinished work to be completed before returning. For example, finish sending any buffered messages.
+
+ The enters the state and remains in it after the method is called until the transition to the state is completed. The transition consists of making successive calls to , , and .
+
+ There is also an asynchronous version of the close method that is initiated by calling .
+
]]>
The communication object is not in a or state and cannot be modified.
@@ -523,15 +523,15 @@
The that specifies how long the close operation has to complete before timing out.
Causes a communication object to transition from its current state into the closed state within a specified interval of time.
- to gracefully transition from any state, other than the state, into the state within a specified interval of time. The method allows any unfinished work to be completed before returning. For example, finish sending any buffered messages.
-
- The enters the state and remains in it after the method is called until the transition to the state is completed. The transition consists of making successive calls to , and .
-
- There is also an asynchronous version of the close method that is initiated by calling .
-
+ to gracefully transition from any state, other than the state, into the state within a specified interval of time. The method allows any unfinished work to be completed before returning. For example, finish sending any buffered messages.
+
+ The enters the state and remains in it after the method is called until the transition to the state is completed. The transition consists of making successive calls to , and .
+
+ There is also an asynchronous version of the close method that is initiated by calling .
+
]]>
The communication object is not in a or state and cannot be modified.
@@ -575,11 +575,11 @@
Occurs when a communication object transitions into the closed state.
- event is raised by the method which is called by the and methods.
-
+ event is raised by the method which is called by the and methods.
+
]]>
@@ -619,11 +619,11 @@
Occurs when a communication object transitions into the closing state.
- event is raised by the method which is called by the and methods.
-
+ event is raised by the method which is called by the and methods.
+
]]>
@@ -734,11 +734,11 @@
The that is returned by a call to the method.
Completes an asynchronous operation to close a communication object.
- method.
-
+ method.
+
]]>
The communication object is not in a or state and cannot be modified.
@@ -785,11 +785,11 @@
The that is returned by a call to the method.
Completes an asynchronous operation to open a communication object.
- method.
-
+ method.
+
]]>
The communication object is not in a or state and cannot be modified.
@@ -830,11 +830,11 @@
Causes a communication object to transition from its current state into the faulted state.
- event is raised by the method which is called by the method.
-
+ event is raised by the method which is called by the method.
+
]]>
@@ -874,11 +874,11 @@
Occurs when a communication object transitions into the faulted state.
- event is raised by the method which is called by the method.
-
+ event is raised by the method which is called by the method.
+
]]>
@@ -951,11 +951,11 @@
if the communication object is in a closed state; otherwise, .
- event occurs.
-
+ event occurs.
+
]]>
@@ -992,11 +992,11 @@
Inserts processing on a communication object after it transitions to the closing state due to the invocation of a synchronous abort operation.
- method calls if the communication object is not already in a state.
-
+ method calls if the communication object is not already in a state.
+
]]>
@@ -1041,13 +1041,13 @@
Inserts processing after a communication object transitions to the closing state due to the invocation of an asynchronous close operation.
The that references the asynchronous on close operation.
- method calls if the communication object is initially in the state.
-
- To insert processing after a communication object transitions to a closing state due to the invocation of a synchronous operation, use the method.
-
+ method calls if the communication object is initially in the state.
+
+ To insert processing after a communication object transitions to a closing state due to the invocation of a synchronous operation, use the method.
+
]]>
The communication object is not in a or state and cannot be modified.
@@ -1096,11 +1096,11 @@
Inserts processing on a communication object after it transitions to the opening state due to the invocation of an asynchronous open operation.
The that references the asynchronous on open operation.
- operation, use the method.
-
+ operation, use the method.
+
]]>
The communication object is not in a or state and cannot be modified.
@@ -1144,13 +1144,13 @@
The that specifies how long the on close operation has to complete before timing out.
Inserts processing on a communication object after it transitions to the closing state due to the invocation of a synchronous close operation.
- method calls if the communication object is initially in the state.
-
- To insert processing after a communication object transitions to a closing state due to the invocation of an asynchronous operation, use the method.
-
+ method calls if the communication object is initially in the state.
+
+ To insert processing after a communication object transitions to a closing state due to the invocation of an asynchronous operation, use the method.
+
]]>
@@ -1191,13 +1191,13 @@
Invoked during the transition of a communication object into the closing state.
- method calls if the communication object is initially in the state.
-
- The method calls (and if the communication object is not already in a state.
-
+ method calls if the communication object is initially in the state.
+
+ The method calls (and if the communication object is not already in a state.
+
]]>
@@ -1234,11 +1234,11 @@
Invoked during the transition of a communication object into the closing state.
- method calls if the communication object is initially in the state.
-
+ method calls if the communication object is initially in the state.
+
]]>
@@ -1278,11 +1278,11 @@
The that is returned by a call to the method.
Completes an asynchronous operation on the close of a communication object.
- method calls if the communication object is not already in a state.
-
+ method calls if the communication object is not already in a state.
+
]]>
The communication object is not in a or state and cannot be modified.
@@ -1326,11 +1326,11 @@
The that is returned by a call to the method.
Completes an asynchronous operation on the open of a communication object.
- method calls (and ).
-
+ method calls (and ).
+
]]>
The communication object is not in a or state and cannot be modified.
@@ -1371,11 +1371,11 @@
Inserts processing on a communication object after it transitions to the faulted state due to the invocation of a synchronous fault operation.
- event is raised by the method which is called by the method.
-
+ event is raised by the method which is called by the method.
+
]]>
@@ -1415,13 +1415,13 @@
The that specifies how long the on open operation has to complete before timing out.
Inserts processing on a communication object after it transitions into the opening state which must complete within a specified interval of time.
- method calls (after calling and before calling ) if the communication object is initially in the state.
-
- To insert processing as a communication object transitions to a opening state due to the invocation of an asynchronous operation, use the method.
-
+ method calls (after calling and before calling ) if the communication object is initially in the state.
+
+ To insert processing as a communication object transitions to a opening state due to the invocation of an asynchronous operation, use the method.
+
]]>
The communication object is not in a or state and cannot be modified.
@@ -1462,11 +1462,11 @@
Invoked during the transition of a communication object into the opened state.
- and methods.
-
+ and methods.
+
]]>
@@ -1503,11 +1503,11 @@
Invoked during the transition of a communication object into the opening state.
- and methods.
-
+ and methods.
+
]]>
@@ -1521,11 +1521,11 @@
Causes a communication object to transition from the created state into the opened state.
- method causes a to enter into the state and calls , , and . The method completes the method by setting the state of the object to the state.
-
+ method causes a to enter into the state and calls , , and . The method completes the method by setting the state of the object to the state.
+
]]>
@@ -1565,23 +1565,23 @@
Causes a communication object to transition from the created state into the opened state.
- is instantiated, it begins in the state. In the state, the object can be configured (for example, properties can be set, or events can be registered), but it is not yet usable to send or receive messages. When called, the method causes a to enter into the state and calls , , and . The method completes the method by setting the state of the object to the state.
-
- In the
-
- state, the is usable (for example, messages can be received), but it is no longer configurable.
-
- There is also an asynchronous version of the open method that is initiated by calling and completed by calling .
-
-### Credentials Capture with Windows Authentication
- When using Windows authentication, credentials used by the service are based on the current context thread. The credentials are obtained when the `Open` method is called.
-
+ is instantiated, it begins in the state. In the state, the object can be configured (for example, properties can be set, or events can be registered), but it is not yet usable to send or receive messages. When called, the method causes a to enter into the state and calls , , and . The method completes the method by setting the state of the object to the state.
+
+ In the
+
+ state, the is usable (for example, messages can be received), but it is no longer configurable.
+
+ There is also an asynchronous version of the open method that is initiated by calling and completed by calling .
+
+### Credentials Capture with Windows Authentication
+ When using Windows authentication, credentials used by the service are based on the current context thread. The credentials are obtained when the `Open` method is called.
+
> [!NOTE]
-> For asynchronous calls, credentials are captured when the is invoked. However, the actual credentials cannot be guaranteed. That is, the credentials of the caller may be switched to another identity. For more information, see [Message Security with a Windows Client](/dotnet/framework/wcf/feature-details/message-security-with-a-windows-client).
-
+> For asynchronous calls, credentials are captured when the is invoked. However, the actual credentials cannot be guaranteed. That is, the credentials of the caller may be switched to another identity. For more information, see [Message Security with a Windows Client](/dotnet/framework/wcf/feature-details/message-security-with-a-windows-client).
+
]]>
The communication object is not in a or state and cannot be modified.
@@ -1630,17 +1630,17 @@
The that specifies how long the open operation has to complete before timing out.
Causes a communication object to transition from the created state into the opened state within a specified interval of time.
- is instantiated, it begins in the state. In the state, the object can be configured (for example, properties can be set, or events can be registered), but it is not yet usable to send or receive messages. When called, the method causes a to enter into the state and calls , , and . The method completes the method by setting the state of the object to the state.
-
- In the
-
- state, the is usable (for example, messages can be received), but it is no longer configurable.
-
- There is also an asynchronous version of the open method that is initiated by calling and completed by calling .
-
+ is instantiated, it begins in the state. In the state, the object can be configured (for example, properties can be set, or events can be registered), but it is not yet usable to send or receive messages. When called, the method causes a to enter into the state and calls , , and . The method completes the method by setting the state of the object to the state.
+
+ In the
+
+ state, the is usable (for example, messages can be received), but it is no longer configurable.
+
+ There is also an asynchronous version of the open method that is initiated by calling and completed by calling .
+
]]>
The communication object is not in a or state and cannot be modified.
@@ -1684,11 +1684,11 @@
Occurs when a communication object transitions into the opened state.
- event is raised by the method which is called by the and methods.
-
+ event is raised by the method which is called by the and methods.
+
]]>
@@ -1728,11 +1728,11 @@
Occurs when a communication object transitions into the opening state.
- event is raised by the method which is called by the and methods.
-
+ event is raised by the method which is called by the and methods.
+
]]>
@@ -1848,11 +1848,11 @@
Throws an exception if the communication object is disposed.
- , or state. A communication object is disposed once is called on it.
-
+ , or state. A communication object is disposed once is called on it.
+
]]>
The communication object is in a or state.
@@ -1887,11 +1887,11 @@
Throws an exception if the communication object the property is not set to the state.
- is called on it, the only state that is both mutable and not disposed is the state.
-
+ is called on it, the only state that is both mutable and not disposed is the state.
+
]]>
The communication object is in a or state.
diff --git a/xml/System.ServiceModel.Channels/ConnectionOrientedTransportBindingElement.xml b/xml/System.ServiceModel.Channels/ConnectionOrientedTransportBindingElement.xml
index 8fbbe0058df..3180d6711bb 100644
--- a/xml/System.ServiceModel.Channels/ConnectionOrientedTransportBindingElement.xml
+++ b/xml/System.ServiceModel.Channels/ConnectionOrientedTransportBindingElement.xml
@@ -783,7 +783,7 @@
## Remarks
This method writes binding-related statements into the WSDL information exposed by a particular contract and is used by Windows Communication Foundation (WCF) to communicate to clients the existence of this custom binding element in the binding stack.
- This method takes two parameters: the and objects. Use the , , and methods to obtain collections of policy assertions that have already been exported at various scopes. Then use this method to add your own policy assertions to the appropriate collection.
+ This method takes two parameters: the and objects. Use the , , and methods to obtain collections of policy assertions that have already been exported at various scopes. Then use this method to add your own policy assertions to the appropriate collection.
The property exposes the for the endpoint that is being exported. This allows this method 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.
diff --git a/xml/System.ServiceModel.Channels/ContextExchangeMechanism.xml b/xml/System.ServiceModel.Channels/ContextExchangeMechanism.xml
index b701be14dda..ab10f48c124 100644
--- a/xml/System.ServiceModel.Channels/ContextExchangeMechanism.xml
+++ b/xml/System.ServiceModel.Channels/ContextExchangeMechanism.xml
@@ -31,7 +31,7 @@
property or the constructor to specify the value of the for a conversation between a client and service.
+ Use the property or the constructor to specify the value of the for a conversation between a client and service.
Service endpoints that require support for the context exchange protocol can make this requirement explicit in their published policy. Policy assertions that represent the requirement for the client to support the context exchange protocol at the SOAP level or that require the enabling of HTTP cookie support can be published by an endpoint. The generation of these assertions into the policy on the service is controlled by the value of the property as follows:
diff --git a/xml/System.ServiceModel.Channels/ContextMessageProperty.xml b/xml/System.ServiceModel.Channels/ContextMessageProperty.xml
index ae22b96c67f..68766a3765b 100644
--- a/xml/System.ServiceModel.Channels/ContextMessageProperty.xml
+++ b/xml/System.ServiceModel.Channels/ContextMessageProperty.xml
@@ -37,15 +37,15 @@
A property used to communicate context between the application and channel layers on either the client or the service.
- that correlates messages that form part of a conversation between a client and a service.
-
- If is `true`, context is established at the channel layer, and all incoming messages on the client and the service have this context property attached by the context channel. If is `false` the is used to attach context to an outgoing message on the client or the service at the application layer.
-
- The can be used on the client or on the service. Alternatively, on the client only, the current context can be obtained or a new context can be set on channel instance using and properties.
-
+ that correlates messages that form part of a conversation between a client and a service.
+
+ If is `true`, context is established at the channel layer, and all incoming messages on the client and the service have this context property attached by the context channel. If is `false` the is used to attach context to an outgoing message on the client or the service at the application layer.
+
+ The can be used on the client or on the service. Alternatively, on the client only, the current context can be obtained or a new context can be set on channel instance using and properties.
+
]]>
@@ -134,11 +134,11 @@
The whose context message property is to be set.
Sets the value of the property in a specified from the current instance of .
- method overwrites the value of the `ContextMessageProperty` property if a value is already set.
-
+ method overwrites the value of the `ContextMessageProperty` property if a value is already set.
+
]]>
diff --git a/xml/System.ServiceModel.Channels/CorrelationCallbackMessageProperty.xml b/xml/System.ServiceModel.Channels/CorrelationCallbackMessageProperty.xml
index 29a72d7e7d7..55d24045dd3 100644
--- a/xml/System.ServiceModel.Channels/CorrelationCallbackMessageProperty.xml
+++ b/xml/System.ServiceModel.Channels/CorrelationCallbackMessageProperty.xml
@@ -20,11 +20,11 @@
Provides an abstract base class for deferring correlation key calculation until all of the correlation data is available.
-
@@ -104,11 +104,11 @@
Provides the value of the correlation data.
Adds required correlation data to the property.
- list. When all required data has been added, the list is empty and returns `true`.
-
+ list. When all required data has been added, the list is empty and returns `true`.
+
]]>
@@ -142,15 +142,15 @@
Called by a correlation protocol when all of the correlation information is available to asynchronously construct the correlation.
A reference to the current asynchronous operation.
- to construct the correlation. Applications must provide an implementation of , which asynchronously performs the correlation calculation of the specified message.
-
- To be notified when the asynchronous operation is complete, call from the `callback` method. If is called before the asynchronous operation is complete, it blocks until the operation completes. If the operation does not complete within the specified time-out interval a is thrown.
-
- This method is an asynchronous version of using the asynchronous design pattern. For more information, see [Asynchronous Programming Overview](/dotnet/standard/asynchronous-programming-patterns/asynchronous-programming-model-apm).
-
+ to construct the correlation. Applications must provide an implementation of , which asynchronously performs the correlation calculation of the specified message.
+
+ To be notified when the asynchronous operation is complete, call from the `callback` method. If is called before the asynchronous operation is complete, it blocks until the operation completes. If the operation does not complete within the specified time-out interval a is thrown.
+
+ This method is an asynchronous version of using the asynchronous design pattern. For more information, see [Asynchronous Programming Overview](/dotnet/standard/asynchronous-programming-patterns/asynchronous-programming-model-apm).
+
]]>
@@ -203,15 +203,15 @@
Returns the message that was prepared asynchronously for correlation.
The message that was prepared for correlation.
- to retrieve the message. Applications must provide an implementation of , which returns the message that was prepared for correlation.
-
- If is called before the asynchronous operation is complete, it blocks until the operation completes. If the operation did not complete within the time-out interval specified in the call to a is thrown when this method is called.
-
- This method completes the asynchronous version of using the asynchronous design pattern. For more information, see [Asynchronous Programming Overview](/dotnet/standard/asynchronous-programming-patterns/asynchronous-programming-model-apm).
-
+ to retrieve the message. Applications must provide an implementation of , which returns the message that was prepared for correlation.
+
+ If is called before the asynchronous operation is complete, it blocks until the operation completes. If the operation did not complete within the time-out interval specified in the call to a is thrown when this method is called.
+
+ This method completes the asynchronous version of using the asynchronous design pattern. For more information, see [Asynchronous Programming Overview](/dotnet/standard/asynchronous-programming-patterns/asynchronous-programming-model-apm).
+
]]>
@@ -241,11 +241,11 @@
Called by a correlation protocol when all of the correlation information is available to construct the correlation.
The correlated message.
- to construct the correlation. Applications must provide an implementation of , which performs the correlation calculation of the specified message.
-
+ to construct the correlation. Applications must provide an implementation of , which performs the correlation calculation of the specified message.
+
]]>
@@ -270,11 +270,11 @@
if all of the required correlation data is present; otherwise, .
- list is empty and returns `true`.
-
+ list is empty and returns `true`.
+
]]>
@@ -350,11 +350,11 @@
When overridden in a derived class, asynchronously performs the correlation calculation for the specified message.
A reference to the current asynchronous operation.
- .
-
+ .
+
]]>
@@ -382,11 +382,11 @@
When overridden in a derived class, returns the message that was prepared asynchronously for correlation.
The correlated message.
- .
-
+ .
+
]]>
@@ -416,11 +416,11 @@
When overridden in a derived class, performs the correlation calculation for the specified message.
The correlated message.
- .
-
+ .
+
]]>
diff --git a/xml/System.ServiceModel.Channels/CustomBinding.xml b/xml/System.ServiceModel.Channels/CustomBinding.xml
index 4193f3e720c..4c4c871733e 100644
--- a/xml/System.ServiceModel.Channels/CustomBinding.xml
+++ b/xml/System.ServiceModel.Channels/CustomBinding.xml
@@ -57,7 +57,7 @@
## Remarks
Use a custom binding when one of the system-provided bindings does not meet the requirements of your service. A custom binding could be used, for example, to enable the use of a new transport or a new encoder at a service endpoint.
- A custom binding is constructed using one of the from a collection of binding elements that are "stacked" in a specific order:
+ A custom binding is constructed using one of the from a collection of binding elements that are "stacked" in a specific order:
- At the top is an optional that allows flowing transactions.
diff --git a/xml/System.ServiceModel.Channels/FaultConverter.xml b/xml/System.ServiceModel.Channels/FaultConverter.xml
index 03b3de043eb..d2ca541277e 100644
--- a/xml/System.ServiceModel.Channels/FaultConverter.xml
+++ b/xml/System.ServiceModel.Channels/FaultConverter.xml
@@ -181,7 +181,7 @@
- If not recognized, convert it by a call to `GetProperty` on the inner channel.
- Transport channels should delegate to to get the default SOAP/WS-Addressing fault converter.
+ Transport channels should delegate to to get the default SOAP/WS-Addressing fault converter.
]]>
@@ -229,7 +229,7 @@
` and override this method to do the following. If a layer can convert the exception it does; otherwise it calls `GetProperty` on its inner channel. Transport channels should delegate to to get the default SOAP/WS-Addressing fault converter.
+ Channels that support fault conversion implement `GetProperty` and override this method to do the following. If a layer can convert the exception it does; otherwise it calls `GetProperty` on its inner channel. Transport channels should delegate to to get the default SOAP/WS-Addressing fault converter.
]]>
@@ -279,7 +279,7 @@
is an abstract class that you must implement. The current method wraps several parameter error tests around a call to that method.
+ is an abstract class that you must implement. The current method wraps several parameter error tests around a call to that method.
]]>
@@ -333,7 +333,7 @@
is an abstract class that you must implement. The current method wraps several error tests around a call to that method.
+ is an abstract class that you must implement. The current method wraps several error tests around a call to that method.
]]>
diff --git a/xml/System.ServiceModel.Channels/HttpRequestMessageExtensionMethods.xml b/xml/System.ServiceModel.Channels/HttpRequestMessageExtensionMethods.xml
index 2425d442d87..6cb64f1125f 100644
--- a/xml/System.ServiceModel.Channels/HttpRequestMessageExtensionMethods.xml
+++ b/xml/System.ServiceModel.Channels/HttpRequestMessageExtensionMethods.xml
@@ -122,11 +122,11 @@
Creates a instance from an instance.
The new instance.
- instance can be read, written and copied just as a traditional instance. The instance can also "read" to retrieve the original instance by calling the extension method.
-
+ instance can be read, written and copied just as a traditional instance. The instance can also "read" to retrieve the original instance by calling the extension method.
+
]]>
diff --git a/xml/System.ServiceModel.Channels/HttpResponseMessageExtensionMethods.xml b/xml/System.ServiceModel.Channels/HttpResponseMessageExtensionMethods.xml
index afbdde83fbd..746cc40c868 100644
--- a/xml/System.ServiceModel.Channels/HttpResponseMessageExtensionMethods.xml
+++ b/xml/System.ServiceModel.Channels/HttpResponseMessageExtensionMethods.xml
@@ -41,11 +41,11 @@
Creates a instance from an instance.
The new instance.
- instance can be read, written and copied just as a traditional instance. The instance can also "read" to retrieve the original instance by calling the extension method.
-
+ instance can be read, written and copied just as a traditional instance. The instance can also "read" to retrieve the original instance by calling the extension method.
+
]]>
diff --git a/xml/System.ServiceModel.Channels/HttpTransportBindingElement.xml b/xml/System.ServiceModel.Channels/HttpTransportBindingElement.xml
index 2a8ae1c6053..03183926af7 100644
--- a/xml/System.ServiceModel.Channels/HttpTransportBindingElement.xml
+++ b/xml/System.ServiceModel.Channels/HttpTransportBindingElement.xml
@@ -1417,7 +1417,7 @@ Console.WriteLine("The scheme of the binding is {0}.",httpBinding.Scheme);
## Remarks
This method writes binding-related statements into the WSDL information exposed by a particular contract and is used by Windows Communication Foundation (WCF) to communicate to clients the existence of this custom binding element in the binding stack.
- This method takes two parameters: the and objects. Use the , , and methods to obtain collections of policy assertions that have already been exported at various scopes. Then use this method to add your own policy assertions to the appropriate collection.
+ This method takes two parameters: the and objects. Use the , , and methods to obtain collections of policy assertions that have already been exported at various scopes. Then use this method to add your own policy assertions to the appropriate collection.
The property exposes the for the endpoint that is being exported. This allows this method 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.
diff --git a/xml/System.ServiceModel.Channels/IBindingRuntimePreferences.xml b/xml/System.ServiceModel.Channels/IBindingRuntimePreferences.xml
index 07720d3b368..cec4ab60706 100644
--- a/xml/System.ServiceModel.Channels/IBindingRuntimePreferences.xml
+++ b/xml/System.ServiceModel.Channels/IBindingRuntimePreferences.xml
@@ -28,9 +28,9 @@
or methods. A class can optionally implement to indicate to callers that this is preferred.
+ In some cases it may be more efficient for a binding to process messages with the synchronous or methods. A class can optionally implement to indicate to callers that this is preferred.
- If a binding does not implement , the Windows Communication Foundation (WCF) Service Model Runtime layer defaults to using the asynchronous versions of the `Receive` and `Request` methods. If a binding does implement , the WCF Service Model Runtime layer checks the value of and uses that to determine whether to call the synchronous versions of these methods ( or ) or the asynchronous versions ( and or and ). If is implemented by the binding and returns `true` from the property, it is recommended that you use the synchronous and methods to receive messages from the channel. If the binding does not implement or returns `false` from the property, it is recommended that you use the asynchronous and or and methods.
+ If a binding does not implement , the Windows Communication Foundation (WCF) Service Model Runtime layer defaults to using the asynchronous versions of the `Receive` and `Request` methods. If a binding does implement , the WCF Service Model Runtime layer checks the value of and uses that to determine whether to call the synchronous versions of these methods ( or ) or the asynchronous versions ( and or and ). If is implemented by the binding and returns `true` from the property, it is recommended that you use the synchronous and methods to receive messages from the channel. If the binding does not implement or returns `false` from the property, it is recommended that you use the asynchronous and or and methods.
Regardless of the value returned by the property, all bindings must still provide valid implementations of both the synchronous and asynchronous versions of the `Receive` methods for the specific channel types implemented. For more information about implementing custom channels, see [Developing Channels](/dotnet/framework/wcf/extending/developing-channels).
diff --git a/xml/System.ServiceModel.Channels/IChannel.xml b/xml/System.ServiceModel.Channels/IChannel.xml
index 837dd250404..bacc3f629f9 100644
--- a/xml/System.ServiceModel.Channels/IChannel.xml
+++ b/xml/System.ServiceModel.Channels/IChannel.xml
@@ -48,30 +48,30 @@
Defines the basic interface that all channel objects must implement. It requires that they implement the state machine interface shared by all communication objects and that they implement a method to retrieve objects from the channel stack.
- interface.
-
- The interface adds the
-
- method to the interface. This method provides a mechanism for retrieving properties from the channel stack regardless of where in the stack those properties live. The term "property" in the method name refers to a piece of information that belongs to one of the channels in the stack. The CLR type for that property is determined by `T`. This method of retrieval is also used on channel factories and channel listeners.
-
- `IChannel` is inherited by each of the channel interfaces associated with the basic message-exchange patterns:
-
-- for receiving messages.
-
-- for sending messages.
-
-- for sending a request.
-
-- for sending a reply.
-
-- for bi-directional messaging.
-
+ Channels must satisfy the contract of a state machine as defined by the interface.
+
+ The interface adds the
+
+ method to the interface. This method provides a mechanism for retrieving properties from the channel stack regardless of where in the stack those properties live. The term "property" in the method name refers to a piece of information that belongs to one of the channels in the stack. The CLR type for that property is determined by `T`. This method of retrieval is also used on channel factories and channel listeners.
+
+ `IChannel` is inherited by each of the channel interfaces associated with the basic message-exchange patterns:
+
+- for receiving messages.
+
+- for sending messages.
+
+- for sending a request.
+
+- for sending a reply.
+
+- for bi-directional messaging.
+
]]>
@@ -117,18 +117,18 @@
Returns a typed object requested, if present, from the appropriate layer in the channel stack.
The typed object requested if it is present or if it is not.
-
diff --git a/xml/System.ServiceModel.Channels/IChannelFactory.xml b/xml/System.ServiceModel.Channels/IChannelFactory.xml
index a65406150e1..8061a0d43d6 100644
--- a/xml/System.ServiceModel.Channels/IChannelFactory.xml
+++ b/xml/System.ServiceModel.Channels/IChannelFactory.xml
@@ -48,13 +48,13 @@
Defines the interface that must be implemented by a channel factory to produce channels.
- interface represents the base interface for channel factories.
-
- Channel factories and their associated channels are generally used by the clients of a service that initiate communication. Listener factories that implement the interface and their associated listeners, by contrast, provide the mechanisms used to accept the channels through which communications with a service is initiated.
-
+ interface represents the base interface for channel factories.
+
+ Channel factories and their associated channels are generally used by the clients of a service that initiate communication. Listener factories that implement the interface and their associated listeners, by contrast, provide the mechanisms used to accept the channels through which communications with a service is initiated.
+
]]>
@@ -100,13 +100,13 @@
Returns a typed object requested, if present, from the appropriate layer in the channel stack.
The typed object requested, if it is present, or if it is not.
- whenever you implement a channel factory. is an excellent way to communicate information along the channel factory stack without having to know what channel factories are below you, or what channel factories above you are interested in performing queries. Define interfaces for people to query on for any interesting information you have. Whenever you do not recognize the type argument for , delegate down to the next channel factory in the stack or return `null` if you are creating a new transport channel at the bottom of the stack.
-
+ whenever you implement a channel factory. is an excellent way to communicate information along the channel factory stack without having to know what channel factories are below you, or what channel factories above you are interested in performing queries. Define interfaces for people to query on for any interesting information you have. Whenever you do not recognize the type argument for , delegate down to the next channel factory in the stack or return `null` if you are creating a new transport channel at the bottom of the stack.
+
]]>
diff --git a/xml/System.ServiceModel.Channels/IChannelFactory`1.xml b/xml/System.ServiceModel.Channels/IChannelFactory`1.xml
index 6a52605199c..75919e2956a 100644
--- a/xml/System.ServiceModel.Channels/IChannelFactory`1.xml
+++ b/xml/System.ServiceModel.Channels/IChannelFactory`1.xml
@@ -55,11 +55,11 @@
The type of channel that the channel factory creates.
Defines the interface that must be implemented by channel factories that create type-specific channels.
- contract allows users to create multiple channels of a given type without having to specify the channel type each time. In other words, defining the channel type as a generic parameter for the channel factory implementing the interface means that it is not necessary to pass the type into the methods. If users want to create different channel types, they can create additional channel factories for each type of channel required. The overload allows you to distinguish the address to which the message is initially sent from the ultimate destination. For a discussion of addressing, see the [Addresses](/dotnet/framework/wcf/feature-details/endpoint-addresses) topic.
-
+ contract allows users to create multiple channels of a given type without having to specify the channel type each time. In other words, defining the channel type as a generic parameter for the channel factory implementing the interface means that it is not necessary to pass the type into the methods. If users want to create different channel types, they can create additional channel factories for each type of channel required. The overload allows you to distinguish the address to which the message is initially sent from the ultimate destination. For a discussion of addressing, see the [Addresses](/dotnet/framework/wcf/feature-details/endpoint-addresses) topic.
+
]]>
@@ -73,11 +73,11 @@
Creates a channel of a specified type to a specified endpoint address.
- overload to distinguish the address to which the message is initially sent from the ultimate destination when you want to do manual routing. Note that any channels created by this channel factory are closed when the channel factory is closed. For a discussion of addressing, see the [Addresses](/dotnet/framework/wcf/feature-details/endpoint-addresses) topic.
-
+ overload to distinguish the address to which the message is initially sent from the ultimate destination when you want to do manual routing. Note that any channels created by this channel factory are closed when the channel factory is closed. For a discussion of addressing, see the [Addresses](/dotnet/framework/wcf/feature-details/endpoint-addresses) topic.
+
]]>
@@ -118,11 +118,11 @@
Creates a channel of a specified type to a specified endpoint address.
A channel of type to the specified endpoint address.
- overload to distinguish the address to which the message is initially sent from the ultimate destination when you want to do manual routing. Note that any channels created by this channel factory are closed when the channel factory is closed.
-
+ overload to distinguish the address to which the message is initially sent from the ultimate destination when you want to do manual routing. Note that any channels created by this channel factory are closed when the channel factory is closed.
+
]]>
@@ -165,11 +165,11 @@
Creates a channel of a specified type to a specified endpoint address and transport address to which messages are sent.
A channel of type to the specified endpoint address and transport address.
- of the final `to` address of the service. You only distinguish between these two addresses when you want to do some kind of manual routing. Note that any channels created by this channel factory are closed when the channel factory is closed. For a discussion of addressing, see the [Addresses](/dotnet/framework/wcf/feature-details/endpoint-addresses) topic.
-
+ of the final `to` address of the service. You only distinguish between these two addresses when you want to do some kind of manual routing. Note that any channels created by this channel factory are closed when the channel factory is closed. For a discussion of addressing, see the [Addresses](/dotnet/framework/wcf/feature-details/endpoint-addresses) topic.
+
]]>
diff --git a/xml/System.ServiceModel.Channels/IChannelListener`1.xml b/xml/System.ServiceModel.Channels/IChannelListener`1.xml
index 5b192b261f9..a68c6eab21a 100644
--- a/xml/System.ServiceModel.Channels/IChannelListener`1.xml
+++ b/xml/System.ServiceModel.Channels/IChannelListener`1.xml
@@ -40,13 +40,13 @@
The type of channel that the channel listener accepts.
Defines the interface that must be implemented by channel listeners to accept type-specific channels.
- or interfaces provide services with the mechanisms used to accept the channels produced by clients that initiate and enable communication with a service.
-
- Implementing the contract allows users to accept multiple channels of a given type without having to specify the channel type each time. In other words, defining the channel type as a generic parameter for the interface means that it is not necessary to pass the type into the methods. If users want to accept different channel types, they can create additional channel listeners for each type of channel required.
-
+ or interfaces provide services with the mechanisms used to accept the channels produced by clients that initiate and enable communication with a service.
+
+ Implementing the contract allows users to accept multiple channels of a given type without having to specify the channel type each time. In other words, defining the channel type as a generic parameter for the interface means that it is not necessary to pass the type into the methods. If users want to accept different channel types, they can create additional channel listeners for each type of channel required.
+
]]>
@@ -59,11 +59,11 @@
Accepts a channel of a specified type for communication with a client.
- overload with the explicit timeout be used. The `timeout` specified for that method overrides any default timeouts set by the system for the service.
-
+ overload with the explicit timeout be used. The `timeout` specified for that method overrides any default timeouts set by the system for the service.
+
]]>
@@ -97,11 +97,11 @@
Accepts a channel of a specified type for communication with a client.
A channel of type accepted by the listener.
- overload with the explicit timeout be used. The `timeout` specified for that method overrides any default timeouts set by the system for the service.
-
+ overload with the explicit timeout be used. The `timeout` specified for that method overrides any default timeouts set by the system for the service.
+
]]>
@@ -138,11 +138,11 @@
Accepts a channel of a specified type for communication with a client within a specified interval of time.
A channel of type accepted by the listener.
- . The `timeout` specified for this method overrides any default timeouts set by the system for the service.
-
+ . The `timeout` specified for this method overrides any default timeouts set by the system for the service.
+
]]>
@@ -155,11 +155,11 @@
Begins an asynchronous operation to accept a channel within a specified or default interval of time.
- overload with the explicit timeout be used. The `timeout` specified for that method overrides any default timeouts set by the system for the service.
-
+ overload with the explicit timeout be used. The `timeout` specified for that method overrides any default timeouts set by the system for the service.
+
]]>
@@ -198,11 +198,11 @@
Begins an asynchronous operation to accept a channel.
The that references the asynchronous acceptance of a channel operation.
- overload with the explicit timeout be used. The `timeout` specified for that method overrides any default timeouts set by the system for the service.
-
+ overload with the explicit timeout be used. The `timeout` specified for that method overrides any default timeouts set by the system for the service.
+
]]>
@@ -243,11 +243,11 @@
Begins an asynchronous operation to accept a channel within a specified interval of time.
The that references the asynchronous acceptance of a channel operation.
- . The `timeout` specified for this method overrides any default timeouts set by the system for the service.
-
+ . The `timeout` specified for this method overrides any default timeouts set by the system for the service.
+
]]>
diff --git a/xml/System.ServiceModel.Channels/IContextManager.xml b/xml/System.ServiceModel.Channels/IContextManager.xml
index 599f57f8e05..1049ece8e4a 100644
--- a/xml/System.ServiceModel.Channels/IContextManager.xml
+++ b/xml/System.ServiceModel.Channels/IContextManager.xml
@@ -29,7 +29,7 @@
with the value set, the context cannot be retrieved on the client using because a new channel that establishes a session is created each time is called to enforce semantics on a channel. This means that even though the context is properly propagated back to the client in this case, it cannot be retrieved using . You can still retrieve it using as shown in the following code.
+ For channels that use with the value set, the context cannot be retrieved on the client using because a new channel that establishes a session is created each time is called to enforce semantics on a channel. This means that even though the context is properly propagated back to the client in this case, it cannot be retrieved using . You can still retrieve it using as shown in the following code.
```csharp
using (new OperationContextScope((IContextChannel)channel))
@@ -75,11 +75,11 @@ using (new OperationContextScope((IContextChannel)channel))
method on it. The channel can also be pre-initialized with context before being opened by calling the method on the channel property. Once the channel is initialized with context it cannot be reset.
+ When context management is enabled the context channel caches the context in its lifetime. Context can be retrieved from the channel through the `IContextManager` channel property by calling method on it. The channel can also be pre-initialized with context before being opened by calling the method on the channel property. Once the channel is initialized with context it cannot be reset.
The following are invariants in this mode:
-- Any call to after the channel is open throws an `InvalidOperationException`.
+- Any call to after the channel is open throws an `InvalidOperationException`.
- Any attempt to send context through the `ContextMessageProperty` in an outgoing message throws `InvalidOperationException`.
@@ -87,7 +87,7 @@ using (new OperationContextScope((IContextChannel)channel))
- The `ContextMessageProperty` on an incoming message is always `null`.
- When context management is not enabled, the context channel does not manage context. It is the application's responsibility to retrieve, manage and apply context through the `ContextMessageProperty`. Any attempt to call or using through the `IContextManager` channel property results in `InvalidOperationException`.
+ When context management is not enabled, the context channel does not manage context. It is the application's responsibility to retrieve, manage and apply context through the `ContextMessageProperty`. Any attempt to call or using through the `IContextManager` channel property results in `InvalidOperationException`.
All HTTP cookies, except for context HTTP cookies, are handled at the channel level. Context HTTP cookies are managed at the application level. This can have unexpected consequences when channels are shared to talk to different instances targeted by . The following table shows how HTTP cookies are affected when is set to either `true` or `false`.
diff --git a/xml/System.ServiceModel.Channels/IDuplexSession.xml b/xml/System.ServiceModel.Channels/IDuplexSession.xml
index 41ea64ea293..9227ea2ed6b 100644
--- a/xml/System.ServiceModel.Channels/IDuplexSession.xml
+++ b/xml/System.ServiceModel.Channels/IDuplexSession.xml
@@ -58,9 +58,9 @@
interface is the union of the inbound session, defined by the interface, and the outbound session, defined by the interface. Either the inbound session or outbound session can be terminated independently of the other. The outbound session can be terminated synchronously by calling or asynchronously by calling .
+ The interface is the union of the inbound session, defined by the interface, and the outbound session, defined by the interface. Either the inbound session or outbound session can be terminated independently of the other. The outbound session can be terminated synchronously by calling or asynchronously by calling .
- The inbound session can be remotely terminated. The associated with the inbound session starts returning `null` when that session is shutdown.
+ The inbound session can be remotely terminated. The associated with the inbound session starts returning `null` when that session is shutdown.
]]>
@@ -217,7 +217,7 @@
signals to the other side of the session that it should return `null` from any outstanding or subsequent calls made to . is idempotent, so calling it again has no effect.
+ Calling signals to the other side of the session that it should return `null` from any outstanding or subsequent calls made to . is idempotent, so calling it again has no effect.
Terminating the outbound session does not affect the incoming session and so makes no statement about the ability to receive messages on the session associated with the input channel.
@@ -277,7 +277,7 @@
signals to the other side of the session that it should return `null` from any outstanding or subsequent calls made to . is idempotent, so calling it again has no effect.
+ Calling signals to the other side of the session that it should return `null` from any outstanding or subsequent calls made to . is idempotent, so calling it again has no effect.
Terminating the outbound session does not affect the incoming session and so makes no statement about the ability to receive messages on the session associated with the input channel.
diff --git a/xml/System.ServiceModel.Channels/IDuplexSessionChannel.xml b/xml/System.ServiceModel.Channels/IDuplexSessionChannel.xml
index 1e7d79f361b..16c5297c59c 100644
--- a/xml/System.ServiceModel.Channels/IDuplexSessionChannel.xml
+++ b/xml/System.ServiceModel.Channels/IDuplexSessionChannel.xml
@@ -74,7 +74,7 @@
The interface indicates that an implements semantics.
- Given an , its associated can be retrieved through the property.
+ Given an , its associated can be retrieved through the property.
]]>
diff --git a/xml/System.ServiceModel.Channels/IInputChannel.xml b/xml/System.ServiceModel.Channels/IInputChannel.xml
index 475d54a9942..d300a638b65 100644
--- a/xml/System.ServiceModel.Channels/IInputChannel.xml
+++ b/xml/System.ServiceModel.Channels/IInputChannel.xml
@@ -59,7 +59,7 @@
The contract includes synchronous and asynchronous variants of receive, try-to-receive and wait-for-a-message functionality.
- The pull model is used typically with an to receive messages: you call (to "pull" a message out of the channel) and then wait for a message to arrive. An alternative usage pattern is to call or , and then call . This approach is common for transactional usages where you start the transaction between the calls to and .
+ The pull model is used typically with an to receive messages: you call (to "pull" a message out of the channel) and then wait for a message to arrive. An alternative usage pattern is to call or , and then call . This approach is common for transactional usages where you start the transaction between the calls to and .
An is not necessarily bound to a single sender. Other channels and channel interfaces can provide a correlation between particular senders and an , but the base contract makes no such restriction. An implementation can create a new for each message or reuse the same for multiple messages and senders.
@@ -79,7 +79,7 @@
method when you want the application processing to continue without waiting for the request to be received. Use the synchronous method when it is acceptable for the current thread to be blocked until the request message is received or the interval of time specified by the `timeout` has been exceeded. The asynchronous operation is available with or without an explicit timeout.
+ Use the asynchronous method when you want the application processing to continue without waiting for the request to be received. Use the synchronous method when it is acceptable for the current thread to be blocked until the request message is received or the interval of time specified by the `timeout` has been exceeded. The asynchronous operation is available with or without an explicit timeout.
]]>
@@ -126,7 +126,7 @@
method when you want the application processing to continue without waiting for the request to be received. Use the synchronous method when it is acceptable for the current thread to be blocked until the request message is received or the interval of time specified by the `timeout` has been exceeded. The asynchronous operation is available with or without an explicit timeout.
+ Use the asynchronous method when you want the application processing to continue without waiting for the request to be received. Use the synchronous method when it is acceptable for the current thread to be blocked until the request message is received or the interval of time specified by the `timeout` has been exceeded. The asynchronous operation is available with or without an explicit timeout.
This method receives notification, through a callback, of the identity of the event handler for the operation. The operation is not complete until a message becomes available in the channel.
@@ -184,7 +184,7 @@
method when you want the application processing to continue without waiting for the request to be received. Use the synchronous method when it is acceptable for the current thread to be blocked until the request message is received or the interval of time specified by the `timeout` has been exceeded. The asynchronous operation is available with or without an explicit timeout.
+ Use the asynchronous method when you want the application processing to continue without waiting for the request to be received. Use the synchronous method when it is acceptable for the current thread to be blocked until the request message is received or the interval of time specified by the `timeout` has been exceeded. The asynchronous operation is available with or without an explicit timeout.
The operation is not complete until either a message becomes available in the channel or the time out occurs.
@@ -247,13 +247,13 @@
method when you want the application processing to continue without waiting. Use the synchronous method when it is acceptable for the current thread to be blocked while it replies to the request message or until the timeout interval is exceeded.
+ Use the asynchronous method when you want the application processing to continue without waiting. Use the synchronous method when it is acceptable for the current thread to be blocked while it replies to the request message or until the timeout interval is exceeded.
The operation is not complete until either a message becomes available in the channel or the timeout occurs.
- If you are going to handle timeouts and not just re-throw or wrap the , then you should call instead of .
+ If you are going to handle timeouts and not just re-throw or wrap the , then you should call instead of .
- If you are not going to treat timeouts specially then just call , otherwise you lose error information.
+ If you are not going to treat timeouts specially then just call , otherwise you lose error information.
@@ -314,7 +314,7 @@
method if you need the application processing to continue without waiting for the message to arrive. Use the synchronous method when it is acceptable for the current thread to be blocked while it waits for a message to arrive in the queue. The thread is blocked up to the specified `timeout`.
+ Use the asynchronous method if you need the application processing to continue without waiting for the message to arrive. Use the synchronous method when it is acceptable for the current thread to be blocked while it waits for a message to arrive in the queue. The thread is blocked up to the specified `timeout`.
This method receives notification, through a callback, of the identity of the event handler for the operation. The operation is not complete until either a message becomes available in the channel or the time out occurs.
@@ -545,9 +545,9 @@
method when it is acceptable for the current thread to be blocked until it receives the request message or exceeds the interval of time specified by `timeout`. Use the asynchronous method when you need the application processing to continue without waiting for the request to be received.
+ Use the synchronous method when it is acceptable for the current thread to be blocked until it receives the request message or exceeds the interval of time specified by `timeout`. Use the asynchronous method when you need the application processing to continue without waiting for the request to be received.
- The synchronous operation is available with or without an explicit timeout.
+ The synchronous operation is available with or without an explicit timeout.
If a message is not available, it blocks until one is available or until the timeout is exceeded.
@@ -591,13 +591,13 @@
method when it is acceptable for the current thread to be blocked until it receives the request message or exceeds the interval of time specified by `timeout`. Use the asynchronous method when you want the application processing to continue without waiting for the request to be received.
+ Use the synchronous method when it is acceptable for the current thread to be blocked until it receives the request message or exceeds the interval of time specified by `timeout`. Use the asynchronous method when you want the application processing to continue without waiting for the request to be received.
- The synchronous operation is available with or without an explicit timeout.
+ The synchronous operation is available with or without an explicit timeout.
If a message is not available, it blocks until one is available or until the timeout is exceeded.
- can be called multiple times or concurrently. Only one call can complete for each message received.
+ can be called multiple times or concurrently. Only one call can complete for each message received.
@@ -649,13 +649,13 @@
method when it is acceptable for the current thread to be blocked until it receives the request message or exceeds the interval of time specified by `timeout`. Use the asynchronous method when you want the application processing to continue without waiting for the request to be received.
+ Use the synchronous method when it is acceptable for the current thread to be blocked until it receives the request message or exceeds the interval of time specified by `timeout`. Use the asynchronous method when you want the application processing to continue without waiting for the request to be received.
- The synchronous operation is available with or without an explicit timeout.
+ The synchronous operation is available with or without an explicit timeout.
If a message is not available, it blocks until one is available or until the timeout is exceeded.
- can be called multiple times or concurrently. Only one call can complete for each message received.
+ can be called multiple times or concurrently. Only one call can complete for each message received.
@@ -712,9 +712,9 @@
, then you should call instead of .
+ If you are going to handle timeouts and not just re-throw or wrap the , then you should call instead of .
- If you are not going to treat timeouts specially then just call , otherwise you will lose error information.
+ If you are not going to treat timeouts specially then just call , otherwise you will lose error information.
@@ -769,13 +769,13 @@
does not result in a message being received or processed in any other way.
+ Calling does not result in a message being received or processed in any other way.
- The method exists primarily for transacted scenarios where the user wants to receive the message using a transaction. When using just normally for this, the user must create the transaction and then call and hope the message arrives before the transaction times out, which may not be possible.
+ The method exists primarily for transacted scenarios where the user wants to receive the message using a transaction. When using just normally for this, the user must create the transaction and then call and hope the message arrives before the transaction times out, which may not be possible.
- Instead, the user can call with whatever time out they want (even infinite), then when a message arrives they can open the transaction, call and be confident that they can get the message back before the transaction expires.
+ Instead, the user can call with whatever time out they want (even infinite), then when a message arrives they can open the transaction, call and be confident that they can get the message back before the transaction expires.
- This method is synchronous, so it blocks the current thread until a message is available or the time out occurs. Use when it is acceptable for the current thread to be blocked while it waits for a message to arrive in the queue. The thread is blocked up to the specified `timeout`. If you need the application processing to continue without waiting, use the asynchronous method.
+ This method is synchronous, so it blocks the current thread until a message is available or the time out occurs. Use when it is acceptable for the current thread to be blocked while it waits for a message to arrive in the queue. The thread is blocked up to the specified `timeout`. If you need the application processing to continue without waiting, use the asynchronous method.
diff --git a/xml/System.ServiceModel.Channels/IInputSessionChannel.xml b/xml/System.ServiceModel.Channels/IInputSessionChannel.xml
index d772caa4fdb..2584cda630b 100644
--- a/xml/System.ServiceModel.Channels/IInputSessionChannel.xml
+++ b/xml/System.ServiceModel.Channels/IInputSessionChannel.xml
@@ -67,7 +67,7 @@
The interface indicates that an implements semantics.
- The associated with an can be retrieved through the property.
+ The associated with an can be retrieved through the property.
]]>
diff --git a/xml/System.ServiceModel.Channels/IOutputChannel.xml b/xml/System.ServiceModel.Channels/IOutputChannel.xml
index 83d26eca48f..cb22c70a09a 100644
--- a/xml/System.ServiceModel.Channels/IOutputChannel.xml
+++ b/xml/System.ServiceModel.Channels/IOutputChannel.xml
@@ -57,7 +57,7 @@
[!INCLUDE [untrusted-data-interface-note](~/includes/untrusted-data-interface-note.md)]
- The interface defines synchronous and asynchronous variants of the operation. It provides a for the destination of the messages sent out on the channel.
+ The interface defines synchronous and asynchronous variants of the operation. It provides a for the destination of the messages sent out on the channel.
]]>
@@ -118,7 +118,7 @@
## Remarks
The destination for messages sent out on an output channel is specified at channel creation time.
- The method does not guarantee the delivery of message to the remote endpoint. If delivery guarantees are required, use the .
+ The method does not guarantee the delivery of message to the remote endpoint. If delivery guarantees are required, use the .
If the message sent is larger that the maximum message size allowed by the binding being used, a is thrown. The maximum message size is set by the property. The default value is 65536 bytes.
@@ -180,7 +180,7 @@
## Remarks
The destination for messages sent out on an output channel is specified at channel creation time.
- The method does not guarantee the delivery of message to the remote endpoint. If delivery guarantees are required, use .
+ The method does not guarantee the delivery of message to the remote endpoint. If delivery guarantees are required, use .
If the message sent is larger that the maximum message size allowed by the binding being used, a is thrown. The maximum message size is set by the property. The default value is 65536 bytes.
@@ -347,9 +347,9 @@
## Remarks
The destination for messages sent out on an output channel is specified at channel creation time.
- The method does not guarantee the delivery of message to the remote endpoint. An implementation of can silently drop messages for a variety of reasons. There may be no more buffer room, for example. If delivery guarantees are required, use .
+ The method does not guarantee the delivery of message to the remote endpoint. An implementation of can silently drop messages for a variety of reasons. There may be no more buffer room, for example. If delivery guarantees are required, use .
- Passing the message into the output channel causes the message to be consumed. After you call , you can no longer inspect the message or call on the message.
+ Passing the message into the output channel causes the message to be consumed. After you call , you can no longer inspect the message or call on the message.
@@ -404,9 +404,9 @@
## Remarks
The destination for messages sent out on an output channel is specified at channel creation time.
- The method does not guarantee the delivery of message to the remote endpoint. An implementation of can silently drop messages for a variety of reasons. There may be no more buffer room, for example. If delivery guarantees are required, use .
+ The method does not guarantee the delivery of message to the remote endpoint. An implementation of can silently drop messages for a variety of reasons. There may be no more buffer room, for example. If delivery guarantees are required, use .
- Passing the message into the output channel causes the message to be consumed. After you call , you can no longer inspect the message or call on the message.
+ Passing the message into the output channel causes the message to be consumed. After you call , you can no longer inspect the message or call on the message.
diff --git a/xml/System.ServiceModel.Channels/IOutputSessionChannel.xml b/xml/System.ServiceModel.Channels/IOutputSessionChannel.xml
index ac27455af97..80513c9de3c 100644
--- a/xml/System.ServiceModel.Channels/IOutputSessionChannel.xml
+++ b/xml/System.ServiceModel.Channels/IOutputSessionChannel.xml
@@ -67,7 +67,7 @@
The interface indicates that an implements semantics.
- The associated with an