Skip to content

Commit cee45ec

Browse files
authored
backtick issues (#6494)
* backtick issues * feedback
1 parent 70b352f commit cee45ec

23 files changed

+89
-93
lines changed

docs/csharp/language-reference/compiler-messages/cs0686.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ class D : I
4343
```
4444

4545
## Example
46-
This error can also occur when declaring events. The event construct automatically generates the `add_``event` and `remove_``event` methods, which could conflict with the methods of the same name in an interface, as in the following sample:
46+
This error can also occur when declaring events. The event construct automatically generates the `add_event` and `remove_event` methods, which could conflict with the methods of the same name in an interface, as in the following sample:
4747

4848
```csharp
4949
// CS0686b.cs

docs/csharp/misc/cs1954.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.assetid: bdec399e-c43d-46d3-a01b-ef3572786fe5
1010
# Compiler Error CS1954
1111
The best overloaded method match 'method' for the collection initializer element cannot be used. Collection initializer 'Add' methods cannot have ref or out parameters.
1212

13-
For a collection class to be initialized by using a collection initializer, the class must have a `public``Add` method that is not a `ref` or `out` parameter.
13+
For a collection class to be initialized by using a collection initializer, the class must have a public `Add` method that is not a `ref` or `out` parameter.
1414

1515
## To correct this error
1616

docs/csharp/programming-guide/concepts/linq/sorting-data.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ foreach (string str in query)
5050
```
5151

5252
#### Primary Descending Sort
53-
The next example demonstrates how to use the `orderby``descending` clause in a LINQ query to sort the strings by their first letter, in descending order.
53+
The next example demonstrates how to use the `orderby descending` clause in a LINQ query to sort the strings by their first letter, in descending order.
5454

5555
```csharp
5656
string[] words = { "the", "quick", "brown", "fox", "jumps" };
@@ -98,7 +98,7 @@ foreach (string str in query)
9898
```
9999

100100
#### Secondary Descending Sort
101-
The next example demonstrates how to use the `orderby``descending` clause in a LINQ query to perform a primary sort, in ascending order, and a secondary sort, in descending order. The strings are sorted primarily by length and secondarily by the first letter of the string.
101+
The next example demonstrates how to use the `orderby descending` clause in a LINQ query to perform a primary sort, in ascending order, and a secondary sort, in descending order. The strings are sorted primarily by length and secondarily by the first letter of the string.
102102

103103
```csharp
104104
string[] words = { "the", "quick", "brown", "fox", "jumps" };

docs/framework/configure-apps/file-schema/wcf/msmqintegration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ Specifies a MSMQ transport for custom binding.
4646

4747
|Attribute|Description|
4848
|---------------|-----------------|
49-
|customDeadLetterQueue|A URI that indicates the location of the per-application dead letter queue, where messages that have expired or failed to be delivered to the application are transferred.<br /><br /> For messages that require ExactlyOnce assurances (that is, `exactlyOnce` is set to `true`), this attribute defaults to the system-wide transactional dead-letter queue in MSMQ.<br /><br /> For messages that require no assurances (that is, `exactlyOnce` is set to `false`), this attribute defaults to `null`.<br /><br /> The value must use the net.msmq scheme. The default is `null`.<br /><br /> If `d``eadLetterQueue` is set to `None` or `System`, then this attribute must be set to `null`. If this attribute is not `null`, then `deadLetterQueue` must be set to `Custom`.|
49+
|customDeadLetterQueue|A URI that indicates the location of the per-application dead letter queue, where messages that have expired or failed to be delivered to the application are transferred.<br /><br /> For messages that require ExactlyOnce assurances (that is, `exactlyOnce` is set to `true`), this attribute defaults to the system-wide transactional dead-letter queue in MSMQ.<br /><br /> For messages that require no assurances (that is, `exactlyOnce` is set to `false`), this attribute defaults to `null`.<br /><br /> The value must use the net.msmq scheme. The default is `null`.<br /><br /> If `deadLetterQueue` is set to `None` or `System`, then this attribute must be set to `null`. If this attribute is not `null`, then `deadLetterQueue` must be set to `Custom`.|
5050
|deadLetterQueue|Specifies the type of dead letter queue to use.<br /><br /> Valid values include<br /><br /> - Custom: Custom deadletter queue.<br />- None: No deadletter queue is to be used.<br />- System: Use the system deadletter queue.<br /><br /> This attribute is of type DeadLetterQueue.|
5151
|durable|A Boolean value that specifies whether the messages processed by this binding are durable or volatile. The default is `true`.<br /><br /> A durable message survives a queue manager crash, while a volatile message does not. Volatile messages are useful when applications require lower latency and can tolerate occasional lost messages.<br /><br /> If `exactlyOnce` is set to `true`, the messages must be durable.|
5252
|exactlyOnce|A Boolean that specifies whether messages processed by this binding will be received exactly once. The default is `true`.<br /><br /> A message can be sent with or without assurances. An assurance enables an application to ensure that a sent message reached the receiving message queue, or if it did not, the application can determine this by reading the dead letter queue.<br /><br /> `exactlyOnce`, when set to `true`, indicates that MSMQ will ensure that a sent message is delivered to the receiving message queue once and only once, and if delivery fails, the message is sent to the dead letter queue.<br /><br /> Messages sent with `exactlyOnce` set to `true` must be sent to a transactional queue only.|

docs/framework/configure-apps/file-schema/wcf/msmqtransport.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ Causes a channel to transfers messages on the MSMQ transport when it is included
5555
|maxPoolSize|A positive integer that specifies the maximum size of the pool. The default is 524288.|
5656
|maxReceivedMessageSize|A positive integer that specifies the maximum message size in bytes including headers. The sender of a message receives a SOAP fault when the message is too large for the receiver. The receiver drops the message and creates an entry of the event in the trace log. The default is 65536.|
5757
|maxRetryCycles|An integer that specifies the maximum number of retry cycles to attempt delivery of messages to the receiving application. The default is <xref:System.Int32.MaxValue>.<br /><br /> A single retry cycle attempts to deliver a message to an application a specified number of times. The number of attempts made is set by the `maxImmediateRetries` attribute. If the application fails to consume the message after the attempts at delivery have been exhausted, the message is sent to a retry queue. Subsequent retry cycles consist of the message being returned from the retry queue to the application queue to attempt delivery to the application again, after a delay specified by the `retryCycleDelay` attribute. The `maxRetryCycles` attribute specifies the number of retry cycles the application uses to attempt to deliver the message.|
58-
|queueTransferProtocol|Specifies the queued communication channel transport that this binding uses. Valid values are<br /><br /> - Native: Use the native MSMQ protocol.<br />- Srmp: Use the Soap Reliable Messaging Protocol (SRMP).<br />- SrmpSecure: Use the Soap Reliable Messaging Protocol Secure (SRMPS) transport.<br /><br /> This attribute is of type <xref:System.ServiceModel.QueueTransferProtocol>.<br /><br /> Since MSMQ does not support Active Directory addressing when using SOAP Reliable Messaging Protocol, you should not set this attribute to Srmp or Srmps when `u``seActiveDirectory` is set to `true`.|
58+
|queueTransferProtocol|Specifies the queued communication channel transport that this binding uses. Valid values are<br /><br /> - Native: Use the native MSMQ protocol.<br />- Srmp: Use the Soap Reliable Messaging Protocol (SRMP).<br />- SrmpSecure: Use the Soap Reliable Messaging Protocol Secure (SRMPS) transport.<br /><br /> This attribute is of type <xref:System.ServiceModel.QueueTransferProtocol>.<br /><br /> Since MSMQ does not support Active Directory addressing when using SOAP Reliable Messaging Protocol, you should not set this attribute to Srmp or Srmps when `useActiveDirectory` is set to `true`.|
5959
|rejectAfterLastRetry|A Boolean value that specifies what action to take for a message that has failed delivery after the maximum number of retries have been attempted.<br /><br /> `true` means that a negative acknowledgment is returned to the sender and the message is dropped; `false` means that the message is sent to the poison message queue. The default is `false`.<br /><br /> If the value is `false`, the receiving application can read the poison message queue to process poison messages (that is, messages that have failed delivery).<br /><br /> MSMQ 3.0 does not support returning a negative acknowledgment to the sender, so this attribute will be ignored in MSMQ 3.0.|
6060
|retryCycleDelay|A <xref:System.TimeSpan> that specifies the time delay between retry cycles when attempting to deliver a message that could not be delivered immediately. The default is 00:10:00.<br /><br /> A single retry cycle attempts to deliver a message to a receiving application a specified number of times. The number of attempts made is specified by the `maxImmediateRetries` attribute. If the application fails to consume the message after the specified number of immediate retries, the message is sent to a retry queue. Subsequent retry cycles consist of the message being returned from the retry queue to the application queue to attempt delivery to the application again, after a delay specified by the `retryCycleDelay` attribute. The number of retry cycles is specified by `maxRetryCycles` attribute.|
6161
|timeToLive|A <xref:System.TimeSpan> that specifies how long the messages are valid before they expired and are put in the dead-letter queue. The default is 1.00:00:00, which means 1 day.<br /><br /> This attribute is set to ensure that time-sensitive messages do not become stale before they are processed by the receiving applications. A message in a queue that is not consumed by the receiving application within the time interval specified is said to be expired. Expired messages are sent to special queue called the dead letter queue. The location of the dead letter queue is set with the `customDeadLetterQueue` attribute or to the appropriate default, based on assurances.|

docs/framework/configure-apps/file-schema/wcf/netmsmqbinding.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ Defines a queued binding suitable for cross-machine communication.
6666
|`maxRetryCycles`|An integer that indicates the number of retry cycles used by the poison-message detection feature. A message becomes a poison message when it fails all delivery attempts of all cycles. The default is 3. For more information, see <xref:System.ServiceModel.MsmqBindingBase.MaxRetryCycles%2A>.|
6767
|`name`|Required attribute. A string that contains the configuration name of the binding. This value should be unique because it is used as an identification for the binding. Starting with [!INCLUDE[netfx40_short](../../../../../includes/netfx40-short-md.md)], bindings and behaviors are not required to have a name. For more information about default configuration and nameless bindings and behaviors, see [Simplified Configuration](../../../../../docs/framework/wcf/simplified-configuration.md) and [Simplified Configuration for WCF Services](../../../../../docs/framework/wcf/samples/simplified-configuration-for-wcf-services.md).|
6868
|`openTimeout`|A <xref:System.TimeSpan> value that specifies the interval of time provided for an open operation to complete. This value should be greater than or equal to <xref:System.TimeSpan.Zero>. The default is 00:01:00.|
69-
|`QueueTransferProtocol`|A valid <xref:System.ServiceModel.QueueTransferProtocol> value that specifies the queued communication channel transport that this binding uses. MSMQ does not support Active Directory addressing when using SOAP Reliable Messaging Protocol. Therefore, you should not set this attribute to `Srmp` or `Srmps` when the `u``seActiveDirectory` attribute is set to `true`.|
69+
|`QueueTransferProtocol`|A valid <xref:System.ServiceModel.QueueTransferProtocol> value that specifies the queued communication channel transport that this binding uses. MSMQ does not support Active Directory addressing when using SOAP Reliable Messaging Protocol. Therefore, you should not set this attribute to `Srmp` or `Srmps` when the `useActiveDirectory` attribute is set to `true`.|
7070
|`receiveErrorHandling`|A <xref:System.ServiceModel.ReceiveErrorHandling> value that specifies how poison and nondispatchable messages are handled.|
7171
|`receiveRetryCount`|An integer that specifies the maximum number of times the queue manager should attempt to send a message before transferring it to the retry queue.|
7272
|`receiveTimeout`|A <xref:System.TimeSpan> value that specifies the interval of time provided for a receive operation to complete. This value should be greater than or equal to <xref:System.TimeSpan.Zero>. The default is 00:10:00.|

docs/framework/data/adonet/code-access-security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ The .NET Framework offers role-based security as well as code access security (C
8383
```
8484

8585
#### KeyRestrictions Syntax
86-
The following example enables the same connection string, enables the use of the `Encrypt` and `Packet``Size` connection string options, but restricts the use of any other connection string options.
86+
The following example enables the same connection string, enables the use of the `Encrypt` and `Packet Size` connection string options, but restricts the use of any other connection string options.
8787

8888
```xml
8989
<connectionStrings>

0 commit comments

Comments
 (0)