Skip to content

Commit ad04dd5

Browse files
mairawBillWagner
authored andcommitted
markdig fixes (#2704)
1 parent 2d162a5 commit ad04dd5

File tree

12 files changed

+40
-40
lines changed

12 files changed

+40
-40
lines changed

xml/System.ServiceModel.Channels/Binding.xml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@
5050
5151
Each binding element provides the specification for building a channel factory on the client and a channel listener on the service. When the channel factory stack is constructed, for example, there is one channel factory in the stack for each binding element in the binding. The same sort of mapping applies to the channel listeners in the stack on the service. Consistency on the client and service is critical for establishing the channel-based connection between these endpoints. Each factory and listener, in turn, processes the sending and accepting of the corresponding channels in the channel stack that connects them, and these channels can then send and receive the messages used to communicate.
5252
53-
Each instance of a <xref:System.ServiceModel.Channels.Binding> has a <xref:System.ServiceModel.Channels.Binding.Name%2A> and <xref:System.ServiceModel.Channels.Binding.Namespace%2A> that together uniquely identify it in the metadata of the service. If no name or namespace is specified, WCF adds a default values for you. The default name is `null` and the default namespace is http://tempuri.org/. This user name for the binding is distinct from the specification of the protocol name, which is specified by the <xref:System.ServiceModel.Channels.Binding.Scheme%2A> property. If you want to add more HTTP bindings, for example, you can name them whatever you want and set all of their schemes to "http". There is no inherent application or machine dispatch based on the <xref:System.ServiceModel.Channels.Binding.Scheme%2A>. So you avoid the common problem of being unable to register additional handlers for well-known protocols. You can also easily work with multiple versions of a binding side-by-side by giving each version a different name.
53+
Each instance of a <xref:System.ServiceModel.Channels.Binding> has a <xref:System.ServiceModel.Channels.Binding.Name%2A> and <xref:System.ServiceModel.Channels.Binding.Namespace%2A> that together uniquely identify it in the metadata of the service. If no name or namespace is specified, WCF adds a default values for you. The default name is `null` and the default namespace is `http://tempuri.org/`. This user name for the binding is distinct from the specification of the protocol name, which is specified by the <xref:System.ServiceModel.Channels.Binding.Scheme%2A> property. If you want to add more HTTP bindings, for example, you can name them whatever you want and set all of their schemes to "http". There is no inherent application or machine dispatch based on the <xref:System.ServiceModel.Channels.Binding.Scheme%2A>. So you avoid the common problem of being unable to register additional handlers for well-known protocols. You can also easily work with multiple versions of a binding side-by-side by giving each version a different name.
5454
5555
The <xref:System.ServiceModel.Channels.Binding> class implements the <xref:System.ServiceModel.IDefaultCommunicationTimeouts> interface to mitigate Denial of Service (DOS) attacks that rely on tying up resources for extended intervals of time. The implementation specifies the communication timeouts values for opening and closing connections and for the reading and writing operations associated with receiving and sending messages. The properties used to get and set these timeouts and their default values operations are summarized in the following table.
5656
@@ -113,7 +113,7 @@
113113
<format type="text/markdown"><![CDATA[
114114
115115
## Remarks
116-
The default name is `null` and the default namespace is http://tempuri.org/.
116+
The default name is `null` and the default namespace is `http://tempuri.org/`.
117117
118118
119119
@@ -1125,7 +1125,7 @@
11251125
</ReturnValue>
11261126
<Docs>
11271127
<summary>Gets or sets the XML namespace of the binding.</summary>
1128-
<value>The XML namespace of the binding. The default value is "http://tempuri.org/".</value>
1128+
<value>The XML namespace of the binding. The default value is <c>"http://tempuri.org/"</c>.</value>
11291129
<remarks>
11301130
<format type="text/markdown"><![CDATA[
11311131

xml/System.ServiceModel.Configuration/HttpTransportElement.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -186,7 +186,7 @@
186186
<format type="text/markdown"><![CDATA[
187187
188188
## Remarks
189-
A local address is one that is on the local LAN or intranet. Always ignores the proxy if the service address begins with http://localhost. You should use the host name rather than localhost if you want clients to go through a proxy when communicating with services on the same machine.
189+
A local address is one that is on the local LAN or intranet. Always ignores the proxy if the service address begins with `http://localhost`. You should use the host name rather than localhost if you want clients to go through a proxy when communicating with services on the same machine.
190190
191191
]]></format>
192192
</remarks>

xml/System.ServiceModel.Description/PolicyVersion.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@
8888
<format type="text/markdown"><![CDATA[
8989
9090
## Remarks
91-
For WS-Policy 1.2 the returned namespace is http://schemas.xmlsoap.org/ws/2004/09/policy. For WS-Policy 1.5 the returned namespace is http://www.w3.org/ns/ws-policy.
91+
For WS-Policy 1.2, the returned namespace is <http://schemas.xmlsoap.org/ws/2004/09/policy>. For WS-Policy 1.5, the returned namespace is <http://www.w3.org/ns/ws-policy>.
9292
9393
]]></format>
9494
</remarks>

xml/System.ServiceModel.Discovery/FindCriteria.xml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -335,7 +335,7 @@
335335
<ReturnType>System.Uri</ReturnType>
336336
</ReturnValue>
337337
<Docs>
338-
<summary>Specifies that scopes are matched by using a case-sensitive comparison (http://schemas.xmlsoap.org/ws/2004/10/discovery/strcmp0) as defined by the <see href="https://schemas.xmlsoap.org/ws/2004/10/discovery/ws-discovery.pdf">WS-Discovery Specification</see>.</summary>
338+
<summary>Specifies that scopes are matched by using a case-sensitive comparison (<c>http://schemas.xmlsoap.org/ws/2004/10/discovery/strcmp0</c>) as defined by the <see href="https://schemas.xmlsoap.org/ws/2004/10/discovery/ws-discovery.pdf">WS-Discovery Specification</see>.</summary>
339339
<remarks>To be added.</remarks>
340340
</Docs>
341341
</Member>
@@ -355,7 +355,7 @@
355355
<ReturnType>System.Uri</ReturnType>
356356
</ReturnValue>
357357
<Docs>
358-
<summary>Specifies that scopes are matched by using the LDAP method (http://schemas.xmlsoap.org/ws/2004/10/discovery/ldap) as defined by the <see href="https://schemas.xmlsoap.org/ws/2004/10/discovery/ws-discovery.pdf">WS-Discovery Specification</see>.</summary>
358+
<summary>Specifies that scopes are matched by using the LDAP method (<c>http://schemas.xmlsoap.org/ws/2004/10/discovery/ldap</c>) as defined by the <see href="https://schemas.xmlsoap.org/ws/2004/10/discovery/ws-discovery.pdf">WS-Discovery Specification</see>.</summary>
359359
<remarks>To be added.</remarks>
360360
</Docs>
361361
</Member>
@@ -395,7 +395,7 @@
395395
<ReturnType>System.Uri</ReturnType>
396396
</ReturnValue>
397397
<Docs>
398-
<summary>Specifies that scopes are matched using the prefix method (http://schemas.xmlsoap.org/ws/2004/10/discovery/rfc2396) as defined by the <see href="https://schemas.xmlsoap.org/ws/2004/10/discovery/ws-discovery.pdf">WS-Discovery Specification</see>.</summary>
398+
<summary>Specifies that scopes are matched using the prefix method (<c>http://schemas.xmlsoap.org/ws/2004/10/discovery/rfc2396</c>) as defined by the <see href="https://schemas.xmlsoap.org/ws/2004/10/discovery/ws-discovery.pdf">WS-Discovery Specification</see>.</summary>
399399
<remarks>To be added.</remarks>
400400
</Docs>
401401
</Member>
@@ -415,7 +415,7 @@
415415
<ReturnType>System.Uri</ReturnType>
416416
</ReturnValue>
417417
<Docs>
418-
<summary>Specifies that scopes are matched by using the UUID method (http://schemas.xmlsoap.org/ws/2004/10/discovery/uuid) as defined by the <see href="https://schemas.xmlsoap.org/ws/2004/10/discovery/ws-discovery.pdf">WS-Discovery Specification</see>.</summary>
418+
<summary>Specifies that scopes are matched by using the UUID method (<c>http://schemas.xmlsoap.org/ws/2004/10/discovery/uuid</c>) as defined by the <see href="https://schemas.xmlsoap.org/ws/2004/10/discovery/ws-discovery.pdf">WS-Discovery Specification</see>.</summary>
419419
<remarks>To be added.</remarks>
420420
</Docs>
421421
</Member>

xml/System.ServiceModel.Dispatcher/XPathMessageContext.xml

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -55,13 +55,13 @@
5555
5656
|Prefix|Namespace|
5757
|------------|---------------|
58-
|s11|http://schemas.xmlsoap.org/soap/envelope|
59-
|s12|http://www.w3.org/2003/05/soap-envelope|
60-
|wsaAugust2004|http://schemas.xmlsoap.org/ws/2004/08/addressing|
61-
|wsa10|http://www.w3.org/2005/08/addressing|
62-
|sm|http://schemas.microsoft.com/serviceModel/2004/05/xpathfunctions|
63-
|tempuri|http://tempuri.org|
64-
|ser|http://schemas.microsoft.com/2003/10/Serialization|
58+
|s11|`http://schemas.xmlsoap.org/soap/envelope`|
59+
|s12|`http://www.w3.org/2003/05/soap-envelope`|
60+
|wsaAugust2004|`http://schemas.xmlsoap.org/ws/2004/08/addressing`|
61+
|wsa10|`http://www.w3.org/2005/08/addressing`|
62+
|sm|`http://schemas.microsoft.com/serviceModel/2004/05/xpathfunctions`|
63+
|tempuri|`http://tempuri.org`|
64+
|ser|`http://schemas.microsoft.com/2003/10/Serialization`|
6565
6666
]]></format>
6767
</remarks>

xml/System.ServiceModel.Routing.Configuration/FilterElement.xml

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -172,14 +172,14 @@
172172
173173
|Filter Type|Description|Filter Data Meaning|Example Filter|
174174
|------------------|-----------------|-------------------------|--------------------|
175-
|Action|Uses the ActionMessageFilter that comes with WCF.|The Action to filter upon.|\<filter name="action1" filterType="Action" filterData="http://ACTION" />|
176-
|Address|Uses the EndpointAddressMessageFilter that comes with WCF with ignore host name == true.|The address to filter upon (in the To header).|\<filter name="address1" filterType="Address" filterData="http://host/vdir/s.svc/b" />|
177-
|AddressPrefix|Uses the PrefixEndpointAddressMessageFilter that comes with WCF with ignore host name == true.|The address to filter upon using longest prefix matching.|\<filter name="prefix1" filterType="AddressPrefix" filterData="http://host" />|
178-
|StrictAnd|A custom AndMessageFilter that always evaluates both conditions before returning.|filterData is not used, instead filter1 and filter2 have the names of the corresponding messages filters (also in the table), which should be ANDed together.|\<filter name="and1" filterType="And" filter1="address1" filter2="action1" />|
179-
|Custom|A user-defined type that extends MessageFilter and has a constructor taking a string.|customType attribute is the fully-qualified type name of the class to create, filterData is the string to pass to the constructor when creating the filter.|\<filter name="custom1" filterType="Custom" customType="CustomAssembly.CustomMsgFilter, CustomAssembly" filterData="Custom Data" />|
180-
|EndpointName|A custom message filter for use solely in the Routing Service, which filters messages based on the name of the service endpoint.|The name of the service endpoint, for example: "serviceEndpoint1". This should be one of the endpoints exposed on the Routing Service.|\<filter name="stock1" filterType="Endpoint" filterData="SvcEndpoint" />|
181-
|MatchAll|Uses the MatchAllMessageFilter that comes with WCF.|N/A|\<filter name="matchAll1" filterType="MatchAll" />|
182-
|XPath|Uses the XPathMessageFilter that comes with WCF.|The XPath query to use when matching messages.|\<filter name="XPath1" filterType="XPath" filterData="//ns:element" />|
175+
|Action|Uses the ActionMessageFilter that comes with WCF.|The Action to filter upon.|`<filter name="action1" filterType="Action" filterData="http://ACTION" />`|
176+
|Address|Uses the EndpointAddressMessageFilter that comes with WCF with ignore host name == true.|The address to filter upon (in the To header).|`<filter name="address1" filterType="Address" filterData="http://host/vdir/s.svc/b" />`|
177+
|AddressPrefix|Uses the PrefixEndpointAddressMessageFilter that comes with WCF with ignore host name == true.|The address to filter upon using longest prefix matching.|`<filter name="prefix1" filterType="AddressPrefix" filterData="http://host" />`|
178+
|StrictAnd|A custom AndMessageFilter that always evaluates both conditions before returning.|filterData is not used, instead filter1 and filter2 have the names of the corresponding messages filters (also in the table), which should be ANDed together.|`<filter name="and1" filterType="And" filter1="address1" filter2="action1" />`|
179+
|Custom|A user-defined type that extends MessageFilter and has a constructor taking a string.|customType attribute is the fully-qualified type name of the class to create, filterData is the string to pass to the constructor when creating the filter.|`<filter name="custom1" filterType="Custom" customType="CustomAssembly.CustomMsgFilter, CustomAssembly" filterData="Custom Data" />`|
180+
|EndpointName|A custom message filter for use solely in the Routing Service, which filters messages based on the name of the service endpoint.|The name of the service endpoint, for example: "serviceEndpoint1". This should be one of the endpoints exposed on the Routing Service.|`<filter name="stock1" filterType="Endpoint" filterData="SvcEndpoint" />`|
181+
|MatchAll|Uses the MatchAllMessageFilter that comes with WCF.|N/A|`<filter name="matchAll1" filterType="MatchAll" />`|
182+
|XPath|Uses the XPathMessageFilter that comes with WCF.|The XPath query to use when matching messages.|`<filter name="XPath1" filterType="XPath" filterData="//ns:element" />`|
183183
184184
]]></format>
185185
</remarks>

xml/System.ServiceModel.Routing.Configuration/NamespaceElement.xml

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -23,13 +23,13 @@
2323
2424
|Prefix|Namespace|
2525
|-|-|
26-
|s11|http://schemas.xmlsoap.org/soap/envelope|
27-
|s12|http://www.w3.org/2003/05/soap-envelope|
28-
|wsaAugust2004|http://schemas.xmlsoap.org/ws/2004/08/addressing|
29-
|wsa10|http://www.w3.org/2005/08/addressing|
30-
|sm|http://schemas.microsoft.com/serviceModel/2004/05/xpathfunctions|
31-
|tempuri|http://tempuri.org|
32-
|ser|http://schemas.microsoft.com/2003/10/Serialization|
26+
|s11|`http://schemas.xmlsoap.org/soap/envelope`|
27+
|s12|`http://www.w3.org/2003/05/soap-envelope`|
28+
|wsaAugust2004|`http://schemas.xmlsoap.org/ws/2004/08/addressing`|
29+
|wsa10|`http://www.w3.org/2005/08/addressing`|
30+
|sm|`http://schemas.microsoft.com/serviceModel/2004/05/xpathfunctions`|
31+
|tempuri|`http://tempuri.org`|
32+
|ser|`http://schemas.microsoft.com/2003/10/Serialization`|
3333
3434
]]></format>
3535
</remarks>

xml/System.Speech.Recognition.SrgsGrammar/SrgsDocument.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -830,7 +830,7 @@ public void WorldSoccerWinners ()
830830
<format type="text/markdown"><![CDATA[
831831
832832
## Remarks
833-
<xref:System.Speech.Recognition.SrgsGrammar.SrgsDocument.XmlBase%2A> property gets a value that is used to resolve relative URIs in a <xref:System.Speech.Recognition.SrgsGrammar.SrgsDocument> object. Suppose the value for <xref:System.Speech.Recognition.SrgsGrammar.SrgsDocument.XmlBase%2A> is "http://www.contoso.com/" and the <xref:System.Speech.Recognition.SrgsGrammar.SrgsDocument> contains a relative rule reference to another document, for example `SrgsRuleRef("ExternalGrammar.grxml")`. This creates the following absolute path to the external document: `http://www.contoso.com/ExternalGrammar.grxml`.
833+
<xref:System.Speech.Recognition.SrgsGrammar.SrgsDocument.XmlBase%2A> property gets a value that is used to resolve relative URIs in a <xref:System.Speech.Recognition.SrgsGrammar.SrgsDocument> object. Suppose the value for <xref:System.Speech.Recognition.SrgsGrammar.SrgsDocument.XmlBase%2A> is `http://www.contoso.com/` and the <xref:System.Speech.Recognition.SrgsGrammar.SrgsDocument> contains a relative rule reference to another document, for example `SrgsRuleRef("ExternalGrammar.grxml")`. This creates the following absolute path to the external document: `http://www.contoso.com/ExternalGrammar.grxml`.
834834
835835
]]></format>
836836
</remarks>

xml/System.Web.Services.Description/HttpBinding.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@
8989
<format type="text/markdown"><![CDATA[
9090
9191
## Remarks
92-
The field value is "http://schemas.xmlsoap.org/wsdl/http/".
92+
The field value is "<http://schemas.xmlsoap.org/wsdl/http/>".
9393
9494
9595

xml/System.Web.Services.Description/Soap12Binding.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@
7979
<format type="text/markdown"><![CDATA[
8080
8181
## Remarks
82-
The field value is the URI "http://schemas.xmlsoap.org/soap/http".
82+
The field value is the URI `"http://schemas.xmlsoap.org/soap/http"`.
8383
8484
]]></format>
8585
</remarks>
@@ -108,7 +108,7 @@
108108
<format type="text/markdown"><![CDATA[
109109
110110
## Remarks
111-
The field value is the URI "http://schemas.xmlsoap.org/wsdl/soap12/".
111+
The field value is the URI `"http://schemas.xmlsoap.org/wsdl/soap12/"`.
112112
113113
]]></format>
114114
</remarks>

0 commit comments

Comments
 (0)