diff --git a/xml/System.IdentityModel.Tokens/EncryptedKeyIdentifierClause.xml b/xml/System.IdentityModel.Tokens/EncryptedKeyIdentifierClause.xml index df3ec120849..795cdf8e2d7 100644 --- a/xml/System.IdentityModel.Tokens/EncryptedKeyIdentifierClause.xml +++ b/xml/System.IdentityModel.Tokens/EncryptedKeyIdentifierClause.xml @@ -256,7 +256,7 @@ property is serialized into XML, it is placed in the <`CarriedKeyName`> element. For encrypted keys, the <`CarriedKeyName`> element is an optional element that associates a user-readable name with a key value. This name can then be used to reference the key using the <`KeyName`> element within the <`KeyInfo`> element. The same <`CarriedKeyName`> element value, unlike an ID value, can occur multiple times within a single document. The value of the key must be the same in all <`EncryptedKey`> elements identified with the same <`CarriedKeyName`> name within an XML document. + When the property is serialized into XML, it is placed in the `` element. For encrypted keys, the `` element is an optional element that associates a user-readable name with a key value. This name can then be used to reference the key using the `` element within the `` element. The same `` element value, unlike an ID value, can occur multiple times within a single document. The value of the key must be the same in all `` elements identified with the same `` name within an XML document. ]]> diff --git a/xml/System.Security.Cryptography.Xml/CipherData.xml b/xml/System.Security.Cryptography.Xml/CipherData.xml index 85cf8658fe2..775d21e943e 100644 --- a/xml/System.Security.Cryptography.Xml/CipherData.xml +++ b/xml/System.Security.Cryptography.Xml/CipherData.xml @@ -36,7 +36,7 @@ ## Examples - The following code example uses the class to create an <`EncryptedData`> element that contains a <`CipherData`> element, and then writes the XML to an XML file. + The following code example uses the class to create an `` element that contains a `` element, and then writes the XML to an XML file. [!code-cpp[cryptgraphy.Xml.EncryptedData#1](~/samples/snippets/cpp/VS_Snippets_CLR/cryptgraphy.Xml.EncryptedData/cpp/encrypteddata.cpp#1)] [!code-csharp[cryptgraphy.Xml.EncryptedData#1](~/samples/snippets/csharp/VS_Snippets_CLR/cryptgraphy.Xml.EncryptedData/CS/encrypteddata.cs#1)] diff --git a/xml/System.Security.Cryptography.Xml/EncryptedXml.xml b/xml/System.Security.Cryptography.Xml/EncryptedXml.xml index 7d5a4c338dc..becb8e0a91f 100644 --- a/xml/System.Security.Cryptography.Xml/EncryptedXml.xml +++ b/xml/System.Security.Cryptography.Xml/EncryptedXml.xml @@ -398,7 +398,7 @@ ## Remarks Use the method to decrypt an element using a symmetric key. - Note that the method only decrypts top-level <`EncryptedData`> tags. In cases where one or more <`EncryptedData`> tags have been encrypted and are contained within higher level <`EncryptedData`> tags, you can call the method separately for each one. See the method for a code example. + Note that the method only decrypts top-level `` tags. In cases where one or more `` tags have been encrypted and are contained within higher level `` tags, you can call the method separately for each one. See the method for a code example. @@ -471,7 +471,7 @@ [!code-csharp[Cryptography.XML.XMLEncMapKeyX509#1](~/samples/snippets/csharp/VS_Snippets_CLR/Cryptography.XML.XMLEncMapKeyX509/CS/sample.cs#1)] [!code-vb[Cryptography.XML.XMLEncMapKeyX509#1](~/samples/snippets/visualbasic/VS_Snippets_CLR/Cryptography.XML.XMLEncMapKeyX509/VB/sample.vb#1)] - The following code example demonstrates how to decrypt a high level <`EncryptedData`> tag that contains another encrypted <`EncryptedData`> tag. + The following code example demonstrates how to decrypt a high level `` tag that contains another encrypted `` tag. [!code-csharp[Cryptography.XML.EncryptedDocument.DecryptDocument-SuperEncryption#1](~/samples/snippets/csharp/VS_Snippets_Misc/Cryptography.XML.EncryptedDocument.DecryptDocument-SuperEncryption/CS/sample.cs#1)] [!code-vb[Cryptography.XML.EncryptedDocument.DecryptDocument-SuperEncryption#1](~/samples/snippets/visualbasic/VS_Snippets_Misc/Cryptography.XML.EncryptedDocument.DecryptDocument-SuperEncryption/VB/sample.vb#1)] diff --git a/xml/System.Security.Cryptography.Xml/KeyInfoX509Data.xml b/xml/System.Security.Cryptography.Xml/KeyInfoX509Data.xml index a9fd0e3de4a..21a2be2155a 100644 --- a/xml/System.Security.Cryptography.Xml/KeyInfoX509Data.xml +++ b/xml/System.Security.Cryptography.Xml/KeyInfoX509Data.xml @@ -546,7 +546,7 @@ property represents the ` element of an XML digital signature using a list of structures contained within. The ` element represents an issuer name and serial number pair, which identify a specific X.509v3 certificate. + The property represents the `` element of an XML digital signature using a list of structures contained within. The `` element represents an issuer name and serial number pair, which identify a specific X.509v3 certificate. The issuer of an X.509 certificate is the name of the certification authority that issued the certificate. Certification authorities assign each certificate they issue a unique serial number. diff --git a/xml/System.Security.Cryptography.Xml/Signature.xml b/xml/System.Security.Cryptography.Xml/Signature.xml index c2b33e6aabc..32b3196f62d 100644 --- a/xml/System.Security.Cryptography.Xml/Signature.xml +++ b/xml/System.Security.Cryptography.Xml/Signature.xml @@ -27,9 +27,9 @@ class represents the <`Signature`> element of an XML signature defined by the XML digital signature specification. The <`Signature`> element is the root element of an XML digital signature. The , , , and properties encapsulate the subelements of the <`Signature`> element. + The class represents the `` element of an XML signature defined by the XML digital signature specification. The `` element is the root element of an XML digital signature. The , , , and properties encapsulate the subelements of the `` element. - For more information about the <`Signature`> element, see the [W3C specification](https://www.w3.org/TR/xmldsig-core/). + For more information about the `` element, see the [W3C specification](https://www.w3.org/TR/xmldsig-core/). @@ -236,7 +236,7 @@ property uses a object to represent the <`KeyInfo`> element of an XML digital signature. + The property uses a object to represent the `` element of an XML digital signature. For more information about XML digital signatures, see the [W3C specification](https://www.w3.org/TR/xmldsig-core/). @@ -329,7 +329,7 @@ property uses a collection of objects to represent the <`Object`> tag of an XML digital signature. + The property uses a collection of objects to represent the `` tag of an XML digital signature. You can also add a to this collection using the method. @@ -370,7 +370,7 @@ property uses a byte array to represent the <`SignatureValue`> element of an XML digital signature contained within. + The property uses a byte array to represent the `` element of an XML digital signature contained within. For more information about XML digital signatures, see the [W3C specification](https://www.w3.org/TR/xmldsig-core/). @@ -409,7 +409,7 @@ property uses the class to represent the <`SignedInfo`> element of an XML digital signature contained within. + The property uses the class to represent the `` element of an XML digital signature contained within. For more information about XML digital signatures, see the [W3C specification](https://www.w3.org/TR/xmldsig-core/). diff --git a/xml/System.Security.Cryptography.Xml/SignedXml.xml b/xml/System.Security.Cryptography.Xml/SignedXml.xml index f1d11eff770..572cb31c1c3 100644 --- a/xml/System.Security.Cryptography.Xml/SignedXml.xml +++ b/xml/System.Security.Cryptography.Xml/SignedXml.xml @@ -27,25 +27,25 @@ class is the .NET Framework implementation of the World Wide Web Consortium (W3C) [XML Signature Syntax and Processing Specification](https://www.w3.org/TR/xmldsig-core/), also known as XMLDSIG (XML Digital Signature). XMLDSIG is a standards-based, interoperable way to sign and verify all or part of an XML document or other data that is addressable from a Uniform Resource Identifier (URI). + The class is the .NET implementation of the World Wide Web Consortium (W3C) [XML Signature Syntax and Processing Specification](https://www.w3.org/TR/xmldsig-core/), also known as XMLDSIG (XML Digital Signature). XMLDSIG is a standards-based, interoperable way to sign and verify all or part of an XML document or other data that is addressable from a Uniform Resource Identifier (URI). - Use the class whenever you need to share signed XML data between applications or organizations in a standard way. Any data signed using this class can be verified by any conforming implementation of the W3C specification for XMLDSIG. + Use the class whenever you need to share signed XML data between applications or organizations in a standard way. Any data signed using this class can be verified by any conforming implementation of the W3C specification for XMLDSIG. The class allows you to create the following three kinds of XML digital signatures: |Signature Type|Description| |--------------------|-----------------| |Enveloped signature|The signature is contained within the XML element being signed.| -|Enveloping signature|The signed XML is contained within the <`Signature`> element.| +|Enveloping signature|The signed XML is contained within the `` element.| |Internal detached signature|The signature and signed XML are in the same document, but neither element contains the other.| There is also a fourth kind of signature called an external detached signature which is when the data and signature are in separate XML documents. External detached signatures are not supported by the class. -## The structure of an XML Signature - XMLDSIG creates a <`Signature`> element, which contains a digital signature of an XML document or other data that is addressable from a URI. The <`Signature`> element can optionally contain information about where to find a key that will verify the signature and which cryptographic algorithm was used for signing. The basic structure is as follows: - -```xml +## The structure of an XML Signature + +XMLDSIG creates a `` element, which contains a digital signature of an XML document or other data that is addressable from a URI. The `` element can optionally contain information about where to find a key that will verify the signature and which cryptographic algorithm was used for signing. The basic structure is as follows: +```xml @@ -59,56 +59,61 @@ AnotherBase64EncodedValue=== - - + ``` - The main parts of this structure are: - - The <`CanonicalizationMethod`> element - Specifies the rules for rewriting the `Signature` element from XML/text into bytes for signature validation. The default value in the .NET Framework is https://www.w3.org/TR/2001/REC-xml-c14n-20010315, which identifies a trustworthy algorithm. This element is represented by the property. +The main parts of this structure are: - The <`SignatureMethod`> element - Specifies the algorithm used for signature generation and validation, which was applied to the <`Signature`> element to produce the value in <`SignatureValue`>. In the example above, the value http://www.w3.org/2000/09/xmldsig#rsa-sha1 identifies an RSA PKCS1 SHA-1 signature. This element is represented by the property. +- The `` element + + Specifies the rules for rewriting the `Signature` element from XML/text into bytes for signature validation. The default value in .NET is , which identifies a trustworthy algorithm. This element is represented by the property. - The <`SignatureValue`> element - Specifies the cryptographic signature for the <`Signature`> element. If this signature does not verify, then some portion of the <`Signature`> block was tampered with, and the document is considered invalid. As long as the <`CanonicalizationMethod`> value is trustworthy, this value is highly resistant to tampering. This element is represented by the property. +- The `` element + + Specifies the algorithm used for signature generation and validation, which was applied to the `` element to produce the value in ``. In the previous example, the value identifies an RSA PKCS1 SHA-1 signature. This element is represented by the property. - The `URI` attribute of the <`Reference`> element - Specifies a data object using a URI reference. This attribute is represented by the property. +- The `` element + + Specifies the cryptographic signature for the `` element. If this signature does not verify, then some portion of the `` block was tampered with, and the document is considered invalid. As long as the `` value is trustworthy, this value is highly resistant to tampering. This element is represented by the property. -- Not specifying the `URI` attribute, that is, setting the property to `null`, means that the receiving application is expected to know the identity of the object. In most cases, a `null` URI will result in an exception being thrown. Do not use a `null` URI, unless your application is interoperating with a protocol which requires it. +- The `URI` attribute of the `` element + + Specifies a data object using a URI reference. This attribute is represented by the property. -- Setting the `URI` attribute to an empty string indicates that the root element of the document is being signed, a form of enveloped signature. + - Not specifying the `URI` attribute, that is, setting the property to `null`, means that the receiving application is expected to know the identity of the object. In most cases, a `null` URI will result in an exception being thrown. Do not use a `null` URI, unless your application is interoperating with a protocol which requires it. -- If the value of `URI` attribute starts with #, then the value must resolve to an element in the current document. This form can be used with any of the supported signature types (enveloped signature, enveloping signature or internal detached signature). + - Setting the `URI` attribute to an empty string indicates that the root element of the document is being signed, a form of enveloped signature. -- Anything else is considered an external resource detached signature and is not supported by the class. + - If the value of `URI` attribute starts with #, then the value must resolve to an element in the current document. This form can be used with any of the supported signature types (enveloped signature, enveloping signature or internal detached signature). - The <`Transforms`> element - Contains an ordered list of <`Transform`> elements that describe how the signer obtained the data object that was digested. A transform algorithm is similar to the canonicalization method, but instead of rewriting the <`Signature`> element, it rewrites the content identified by the `URI` attribute of the <`Reference`> element. The <`Transforms`> element is represented by the class. + - Anything else is considered an external resource detached signature and is not supported by the class. -- Each transform algorithm is defined as taking either XML (an XPath node-set) or bytes as input. If the format of the current data differs from the transform input requirements, conversion rules are applied. +- The `` element + + Contains an ordered list of `` elements that describe how the signer obtained the data object that was digested. A transform algorithm is similar to the canonicalization method, but instead of rewriting the `` element, it rewrites the content identified by the `URI` attribute of the `` element. The `` element is represented by the class. -- Each transform algorithm is defined as producing either XML or bytes as the output. + - Each transform algorithm is defined as taking either XML (an XPath node-set) or bytes as input. If the format of the current data differs from the transform input requirements, conversion rules are applied. -- If the output of the last transform algorithm is not defined in bytes (or no transforms were specified), then the [canonicalization method](https://www.w3.org/TR/2001/REC-xml-c14n-20010315) is used as an implicit transform (even if a different algorithm was specified in the <`CanonicalizationMethod`> element). + - Each transform algorithm is defined as producing either XML or bytes as the output. -- A value of http://www.w3.org/2000/09/xmldsig#enveloped-signature for the transform algorithm encodes a rule which is interpreted as remove the <`Signature`> element from the document. Otherwise, a verifier of an enveloped signature will digest the document, including the signature, but the signer would have digested the document before the signature was applied, leading to different answers. + - If the output of the last transform algorithm is not defined in bytes (or no transforms were specified), then the [canonicalization method](https://www.w3.org/TR/2001/REC-xml-c14n-20010315) is used as an implicit transform (even if a different algorithm was specified in the `` element). - The <`DigestMethod`> element - Identifies the digest (cryptographic hash) method to apply on the transformed content identified by the `URI` attribute of the <`Reference`> element. This is represented by the property. + - A value of for the transform algorithm encodes a rule which is interpreted as remove the `` element from the document. Otherwise, a verifier of an enveloped signature will digest the document, including the signature, but the signer would have digested the document before the signature was applied, leading to different answers. + +- The `` element + + Identifies the digest (cryptographic hash) method to apply on the transformed content identified by the `URI` attribute of the `` element. This is represented by the property. ## Choosing a canonicalization method - Unless interoperating with a specification which requires the use of a different value, we recommend that you use the default canonicalization method in the .NET Framework which is the XML-C14N 1.0 algorithm, whose value is https://www.w3.org/TR/2001/REC-xml-c14n-20010315. The XML-C14N 1.0 algorithm is required to be supported by all implementations of XMLDSIG, particularly as it is an implicit final transform to apply. + Unless interoperating with a specification which requires the use of a different value, we recommend that you use the default .NET canonicalization method, which is the XML-C14N 1.0 algorithm, whose value is . The XML-C14N 1.0 algorithm is required to be supported by all implementations of XMLDSIG, particularly as it is an implicit final transform to apply. - There are versions of canonicalization algorithms which support preserving comments. Comment-preserving canonicalization methods are not recommended because they violate the "sign what is seen" principle. That is, the comments in a <`Signature`> element will not alter the processing logic for how the signature is performed, merely what the signature value is. When combined with a weak signature algorithm, allowing the comments to be included gives an attacker unnecessary freedom to force a hash collision, making a tampered document appear legitimate. In the .NET Framework, only built-in canonicalizers are supported by default. To support additional or custom canonicalizers, see the property. If the document uses a canonicalization method that is not in the collection represented by the property, then the method will return `false`. + There are versions of canonicalization algorithms which support preserving comments. Comment-preserving canonicalization methods are not recommended because they violate the "sign what is seen" principle. That is, the comments in a `` element will not alter the processing logic for how the signature is performed, merely what the signature value is. When combined with a weak signature algorithm, allowing the comments to be included gives an attacker unnecessary freedom to force a hash collision, making a tampered document appear legitimate. In the .NET Framework, only built-in canonicalizers are supported by default. To support additional or custom canonicalizers, see the property. If the document uses a canonicalization method that is not in the collection represented by the property, then the method will return `false`. > [!NOTE] > An extremely defensive application can remove any values it does not expect signers to use from the collection. ## Are the Reference values safe from tampering? - Yes, the <`Reference`> values are safe from tampering. The .NET framework verifies the <`SignatureValue`> computation before processing any of the <`Reference`> values and their associated transforms, and will abort early to avoid potentially malicious processing instructions. + Yes, the `` values are safe from tampering. .NET verifies the `` computation before processing any of the `` values and their associated transforms, and will abort early to avoid potentially malicious processing instructions. ## Choosing the elements to sign We recommend that you use the value of "" for the `URI` attribute (or set the property to an empty string), if possible. This means the whole document is considered for the digest computation, which means the whole document is protected from tampering. @@ -120,20 +125,20 @@ If you need to accept documents which are only partially protected and you want to ensure that you are reading the same content that the signature protected, use the method. ## Security considerations about the KeyInfo element - The data in the optional <`KeyInfo`> element (that is, the property), which contains a key to validate the signature, should not be trusted. + The data in the optional `` element (that is, the property), which contains a key to validate the signature, should not be trusted. In particular, when the value represents a bare RSA, DSA or ECDSA public key, the document could have been tampered with, despite the method reporting that the signature is valid. This can happen because the entity doing the tampering just has to generate a new key and re-sign the tampered document with that new key. So, unless your application verifies that the public key is an expected value, the document should be treated as if it were tampered with. This requires that your application examine the public key embedded within the document and verify it against a list of known values for the document context. For example, if the document could be understood to be issued by a known user, you'd check the key against a list of known keys used by that user. You can also verify the key after processing the document by using the method, instead of using the method. But, for the optimal security, you should verify the key beforehand. - Alternately, consider trying the user's registered public keys, rather than reading what's in the <`KeyInfo`> element. + Alternately, consider trying the user's registered public keys, rather than reading what's in the `` element. ## Security considerations about the X509Data element - The optional <`X509Data`> element is a child of the <`KeyInfo`> element and contains one or more X509 certificates or identifiers for X509 certificates. The data in the <`X509Data`> element should also not be inherently trusted. + The optional `` element is a child of the `` element and contains one or more X509 certificates or identifiers for X509 certificates. The data in the `` element should also not be inherently trusted. - When verifying a document with the embedded <`X509Data`> element, the .NET Framework verifies only that the data resolves to an X509 certificate whose public key can be successfully used to validate the document signature. Unlike calling the method with the `verifySignatureOnly` parameter set to `false`, no revocation check is performed, no chain trust is checked, and no expiration is verified. Even if your application extracts the certificate itself and passes it to the method with the `verifySignatureOnly` parameter set to `false`, that is still not sufficient validation to prevent document tampering. The certificate still needs to be verified as being appropriate for the document being signed. + When verifying a document with the embedded `` element, .NET verifies only that the data resolves to an X509 certificate whose public key can be successfully used to validate the document signature. Unlike calling the method with the `verifySignatureOnly` parameter set to `false`, no revocation check is performed, no chain trust is checked, and no expiration is verified. Even if your application extracts the certificate itself and passes it to the method with the `verifySignatureOnly` parameter set to `false`, that is still not sufficient validation to prevent document tampering. The certificate still needs to be verified as being appropriate for the document being signed. - Using an embedded signing certificate can provide useful key rotation strategies, whether in the <`X509Data`> section or in the document content. When using this approach an application should extract the certificate manually and perform validation similar to: + Using an embedded signing certificate can provide useful key rotation strategies, whether in the `` section or in the document content. When using this approach an application should extract the certificate manually and perform validation similar to: - The certificate was issued directly or via a chain by a Certificate Authority (CA) whose public certificate is embedded in the application. @@ -146,9 +151,9 @@ - The certificate subject is verified as being appropriate to the current document. ## Choosing the transform algorithm - If you are interoperating with a specification which has dictated specific values (such as XrML), then you need to follow the specification. If you have an enveloped signature (such as when signing the whole document), then you need to use http://www.w3.org/2000/09/xmldsig#enveloped-signature (represented by the class). You can specify the implicit XML-C14N transform as well, but it's not necessary. For an enveloping or detached signature, no transforms are required. The implicit XML-C14N transform takes care of everything. + If you are interoperating with a specification which has dictated specific values (such as XrML), then you need to follow the specification. If you have an enveloped signature (such as when signing the whole document), then you need to use (represented by the class). You can specify the implicit XML-C14N transform as well, but it's not necessary. For an enveloping or detached signature, no transforms are required. The implicit XML-C14N transform takes care of everything. - With the security updated introduced by the [Microsoft Security Bulletin MS16-035](https://docs.microsoft.com/security-updates/securitybulletins/2016/ms16-035), the .NET Framework has restricted what transforms can be used in document verification by default, with untrusted transforms causing to always return `false`. In particular, transforms which require additional input (specified as child elements in the XML) are no longer allowed due to their susceptibility of abuse by malicious users. The W3C advises avoiding the XPath and XSLT transforms, which are the two main transforms affected by these restrictions. + With the security updated introduced by the [Microsoft Security Bulletin MS16-035](https://docs.microsoft.com/security-updates/securitybulletins/2016/ms16-035), .NET has restricted what transforms can be used in document verification by default, with untrusted transforms causing to always return `false`. In particular, transforms which require additional input (specified as child elements in the XML) are no longer allowed due to their susceptibility of abuse by malicious users. The W3C advises avoiding the XPath and XSLT transforms, which are the two main transforms affected by these restrictions. ## The problem with external references If an application does not verify that external references seem appropriate for the current context, they can be abused in ways that provide for many security vulnerabilities (including Denial of Service, Distributed Reflection Denial of Service, Information Disclosure, Signature Bypass, and Remote Code Execution). Even if an application were to validate the external reference URI, there would remain a problem of the resource being loaded twice: once when your application reads it, and once when reads it. Since there's no guarantee that the application read and document verify steps have the same content, the signature does not provide trustworthiness. @@ -351,7 +356,7 @@ method adds an <`Object`> element that represents an object to be signed to the <`Signature`> element of an XML digital signature. + The method adds an `` element that represents an object to be signed to the `` element of an XML digital signature. The method internally calls the method of the object encapsulated by the object. You can also add a object by directly calling the method from the property. @@ -402,7 +407,7 @@ method adds a <`Reference`> element to the object that describes a digest method, digest value, and transform to use for creating an XML digital signature. The <`Reference`> element is a subelement of the <`SignedInfo`> element. + The method adds a `` element to the object that describes a digest method, digest value, and transform to use for creating an XML digital signature. The `` element is a subelement of the `` element. The method internally calls the method of the object encapsulated by the object. You can also add a object by directly calling the method from the property. @@ -1072,7 +1077,7 @@ property represents the <`KeyInfo`> element of an XML digital signature using a object contained within the property. The <`KeyInfo`> element is a subelement of the <`Signature`> element. + The property represents the `` element of an XML digital signature using a object contained within the property. The `` element is a subelement of the `` element. Use the property to embed key-related information intended to help identify the key necessary for validating an XML document. @@ -1307,7 +1312,7 @@ property represents the <`Signature`> element of an XML digital signature using a object contained within the property. The <`Signature`> element is the root element used for XML digital signature creation and verification. + The property represents the `` element of an XML digital signature using a object contained within the property. The `` element is the root element used for XML digital signature creation and verification. Use the property to retrieve the object used by the object. @@ -1432,9 +1437,9 @@ property represents the <`SignatureMethod`> element of an XML digital signature using a Uniform Resource Identifier (URI) string contained within the property. The <`SignatureMethod`> element is a subelement of the <`SignedInfo`> element. + The property represents the `` element of an XML digital signature using a Uniform Resource Identifier (URI) string contained within the property. The `` element is a subelement of the `` element. - Use the property to retrieve the <`SignatureMethod`> URI used by the object. This property is read only. For more information about programmatically specifying a URI for the <`SignatureMethod`> element, see the property. + Use the property to retrieve the `` URI used by the object. This property is read only. For more information about programmatically specifying a URI for the `` element, see the property. For more information about the `` element, see the [XMLDSIG specification](https://www.w3.org/TR/xmldsig-core/). @@ -1472,7 +1477,7 @@ property represents the <`SignatureValue`> element of an XML digital signature using an array of bytes contained within the property. The <`SignatureValue`> element is a subelement of the <`Signature>` element. + The property represents the `` element of an XML digital signature using an array of bytes contained within the property. The `` element is a subelement of the `` element. Use the property to retrieve the value of the XML digital signature. This property is automatically populated when you make a successful call to the method. @@ -1512,7 +1517,7 @@ property represents the <`SignedInfo`> element of an XML digital signature using an array of bytes contained within the property. The <`SignedInfo`> element is a subelement of the <`Signature>` element. + The property represents the `` element of an XML digital signature using an array of bytes contained within the property. The `` element is a subelement of the `` element. Use the property to retrieve the object that is used by the object to create an XML digital signature. @@ -1636,11 +1641,11 @@ field is "http://www.w3.org/2002/07/decrypt#XML". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. - For more information, see the World Wide Web Consortium (W3C) specification at http://www.w3.org/2002/07/decrypt#XML. + For more information, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/2002/07/decrypt#XML). ]]> @@ -1674,13 +1679,13 @@ field is "http://www.w3.org/2000/09/xmldsig#base64". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. The class implements the transform described by the field. - For more information, see the World Wide Web Consortium (W3C) specification at http://www.w3.org/2000/09/xmldsig#base64. + For more information, see the [World Wide Web Consortium (W3C) schema](https://www.w3.org/2000/09/xmldsig#base64). @@ -1723,7 +1728,7 @@ field is `http://www.w3.org/TR/2001/REC-xml-c14n-20010315`. + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. @@ -1774,7 +1779,7 @@ field is `http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments`. + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. @@ -1817,7 +1822,7 @@ field is `http://www.w3.org/TR/2001/REC-xml-c14n-20010315`. + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. @@ -1860,7 +1865,7 @@ field is `http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments`. + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. @@ -1903,11 +1908,11 @@ field is "http://www.w3.org/2000/09/xmldsig#dsa-sha1". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. - For more information, see the World Wide Web Consortium (W3C) specification at http://www.w3.org/2000/09/xmldsig#dsa-sha1. + For more information, see the [World Wide Web Consortium (W3C) schema](https://www.w3.org/2000/09/xmldsig#dsa-sha1). ]]> @@ -1941,13 +1946,13 @@ field is "http://www.w3.org/2000/09/xmldsig#enveloped-signature". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. The class implements the transform described by the field. - For more information, see the World Wide Web Consortium (W3C) specification at http://www.w3.org/2000/09/xmldsig#enveloped-signature. + For more information, see the [World Wide Web Consortium (W3C) schema](https://www.w3.org/2000/09/xmldsig#enveloped-signature). @@ -1990,13 +1995,13 @@ field is "http://www.w3.org/2001/10/xml-exc-c14n#". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. The class implements the transform described by the field. - For more information, see the World Wide Web Consortium (W3C) specification at http://www.w3.org/2001/10/xml-exc-c14n#. + For more information, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/2001/10/xml-exc-c14n). @@ -2039,13 +2044,13 @@ field is "http://www.w3.org/2001/10/xml-exc-c14n#WithComments". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. The class implements the transform described by the field. - For more information, see the World Wide Web Consortium (W3C) specification at http://www.w3.org/2001/10/xml-exc-c14n#WithComments. + For more information, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/2001/10/xml-exc-c14n#WithComments). @@ -2089,11 +2094,11 @@ field is "http://www.w3.org/2000/09/xmldsig#hmac-sha1". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. - For more information, see the World Wide Web Consortium (W3C) specification at http://www.w3.org/2000/09/xmldsig#hmac-sha1. + For more information, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/2000/09/xmldsig#hmac-sha1). ]]> @@ -2128,11 +2133,11 @@ field is "http://www.w3.org/2000/09/xmldsig#minimal". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. - For more information, see the World Wide Web Consortium (W3C) specification at http://www.w3.org/2000/09/xmldsig#minimal. + For more information, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/2000/09/xmldsig#minimal). ]]> @@ -2167,11 +2172,11 @@ field is "http://www.w3.org/2000/09/xmldsig#". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. - For more information, see the World Wide Web Consortium (W3C) specification at http://www.w3.org/2000/09/xmldsig#. + For more information, see the [World Wide Web Consortium (W3C) schema](https://www.w3.org/2000/09/xmldsig). ]]> @@ -2206,11 +2211,11 @@ field is "http://www.w3.org/2000/09/xmldsig#rsa-sha1". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. - For more information, see the World Wide Web Consortium (W3C) specification at http://www.w3.org/2000/09/xmldsig#rsa-sha1. + For more information, see the [World Wide Web Consortium (W3C) schema](https://www.w3.org/2000/09/xmldsig#rsa-sha1). ]]> @@ -2241,11 +2246,11 @@ field is "http://www.w3.org/2001/04/xmldsig-more#rsa-sha256". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. - For more information, see the World Wide Web Consortium (W3C) specification at [https://www.w3.org/2001/04/xmldsig-more#rsa-sha256](https://www.w3.org/2001/04/xmldsig-more#rsa-sha256). + For more information, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/2001/04/xmldsig-more#rsa-sha256). ]]> @@ -2276,11 +2281,11 @@ field is "http://www.w3.org/2001/04/xmldsig-more#rsa-sha384". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. - For more information, see the World Wide Web Consortium (W3C) specification at [https://www.w3.org/2001/04/xmldsig-more#rsa-sha384](https://www.w3.org/2001/04/xmldsig-more#rsa-sha384). + For more information, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/2001/04/xmldsig-more#rsa-sha384). ]]> @@ -2311,11 +2316,11 @@ field is "http://www.w3.org/2001/04/xmldsig-more#rsa-sha512". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. - For more information, see the World Wide Web Consortium (W3C) specification at [https://www.w3.org/2001/04/xmldsig-more#rsa-sha512](https://www.w3.org/2001/04/xmldsig-more#rsa-sha512). + For more information, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/2001/04/xmldsig-more#rsa-sha512). ]]> @@ -2350,11 +2355,11 @@ field is "http://www.w3.org/2000/09/xmldsig#sha1". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. - For more information, see the World Wide Web Consortium (W3C) specification at http://www.w3.org/2000/09/xmldsig#sha1. + For more information, see the [World Wide Web Consortium (W3C) schema](https://www.w3.org/2000/09/xmldsig#sha1). ]]> @@ -2385,11 +2390,11 @@ field is "http://www.w3.org/2001/04/xmlenc#sha256". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. - For more information, see the World Wide Web Consortium (W3C) specification at [http://www.w3.org/2001/04/xmlenc#sha256](https://www.w3.org/2001/04/xmlenc#sha256). + For more information, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/2001/04/xmlenc#sha256). ]]> @@ -2420,11 +2425,11 @@ field is "http://www.w3.org/2001/04/xmldsig-more#sha384". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. - For more information, see the World Wide Web Consortium (W3C) specification at [https://www.w3.org/2001/04/xmldsig-more#sha384](https://www.w3.org/2001/04/xmldsig-more#sha384). + For more information, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/2001/04/xmldsig-more#sha384). ]]> @@ -2455,11 +2460,11 @@ field is "http://www.w3.org/2001/04/xmlenc#sha512". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. - For more information, see the World Wide Web Consortium (W3C) specification at [http://www.w3.org/2001/04/xmlenc#sha512](https://www.w3.org/2001/04/xmlenc#sha512). + For more information, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/2001/04/xmlenc#sha512). ]]> @@ -2493,13 +2498,13 @@ field is "http://www.w3.org/TR/1999/REC-xpath-19991116". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. The class implements the transform described by the field. - For more information, see the World Wide Web Consortium (W3C) specification at http://www.w3.org/TR/1999/REC-xpath-19991116. + For more information, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/TR/1999/REC-xpath-19991116). @@ -2541,13 +2546,13 @@ field is "http://www.w3.org/TR/1999/REC-xslt-19991116". + The value of the field is . Use this field to conveniently supply a value to one of the URI attributes of an element used for XMLDSIG. The class implements the transform described by the field. - For more information, see the World Wide Web Consortium (W3C) specification at http://www.w3.org/TR/1999/REC-xslt-19991116. + For more information, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/TR/1999/REC-xslt-19991116). @@ -2601,4 +2606,4 @@ - \ No newline at end of file + diff --git a/xml/System.Security.Cryptography.Xml/Transform.xml b/xml/System.Security.Cryptography.Xml/Transform.xml index 62f00dd0608..993fef8f320 100644 --- a/xml/System.Security.Cryptography.Xml/Transform.xml +++ b/xml/System.Security.Cryptography.Xml/Transform.xml @@ -27,7 +27,7 @@ element describes how the signer transformed the data object that was signed. The verifier of a document then uses the <`Transform`> element to transform the signed data in the same manner. If the verifier cannot transform the signed data in the same manner, the document cannot be verified. + When performing XML signing and verification, the `` element describes how the signer transformed the data object that was signed. The verifier of a document then uses the `` element to transform the signed data in the same manner. If the verifier cannot transform the signed data in the same manner, the document cannot be verified. Use a class that derives from the class whenever you need to add one or more transform objects to an encrypted XML document or to a signed XML document. diff --git a/xml/System.Security.Cryptography.Xml/X509IssuerSerial.xml b/xml/System.Security.Cryptography.Xml/X509IssuerSerial.xml index 96d60a3e098..820de7cc4d7 100644 --- a/xml/System.Security.Cryptography.Xml/X509IssuerSerial.xml +++ b/xml/System.Security.Cryptography.Xml/X509IssuerSerial.xml @@ -30,13 +30,13 @@ structure represents the ` element of an XML digital signature defined by the XML digital signature specification. The ` element is the subelement of the <`X509Data`> element that contains an X.509v3 certificate issuer's distinguished name and serial number pair. The distinguished name and serial number pair help identify a specific X.509v3 certificate. + The structure represents the `` element of an XML digital signature defined by the XML digital signature specification. The `` element is the subelement of the `` element that contains an X.509v3 certificate issuer's distinguished name and serial number pair. The distinguished name and serial number pair help identify a specific X.509v3 certificate. The issuer of an X.509 certificate is the name of the certification authority that issued the certificate. Certification authorities assign each certificate they issue a unique serial number for identification purposes. Use the structure to specify a certificate issuer's distinguished name and serial number pair when using the class. You can add an structure to the class using the property. Alternatively, you can add string values that represent the X.509 certificate issuer's distinguished name and serial number pair using the method. - For more information about the ` element, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/TR/xmldsig-core/). + For more information about the `` element, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/TR/xmldsig-core/). @@ -83,9 +83,9 @@ property represents an X.509 certificate issuer's distinguished name specified in the ` element. + The property represents an X.509 certificate issuer's distinguished name specified in the `` element. - For more information about the ` element, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/TR/xmldsig-core/). + For more information about the `` element, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/TR/xmldsig-core/). @@ -132,9 +132,9 @@ property represents an X.509 certificate issuer's serial number specified in the ` element. + The property represents an X.509 certificate issuer's serial number specified in the `` element. - For more information about the ` element, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/TR/xmldsig-core/). + For more information about the `` element, see the [World Wide Web Consortium (W3C) specification](https://www.w3.org/TR/xmldsig-core/). diff --git a/xml/System.ServiceModel.Activities.Description/WorkflowRuntimeEndpoint.xml b/xml/System.ServiceModel.Activities.Description/WorkflowRuntimeEndpoint.xml index 3aef7689f2c..30192bfd955 100644 --- a/xml/System.ServiceModel.Activities.Description/WorkflowRuntimeEndpoint.xml +++ b/xml/System.ServiceModel.Activities.Description/WorkflowRuntimeEndpoint.xml @@ -24,9 +24,9 @@ sub-element in the SqlWorkflowInstanceStore element is an optional element that specifies parameters for a workflow instance control endpoint. The Workflow Management Service uses this endpoint to issue control commands to the service host. + The `` sub-element in the SqlWorkflowInstanceStore element is an optional element that specifies parameters for a workflow instance control endpoint. The Workflow Management Service uses this endpoint to issue control commands to the service host. - If the <`workflowInstanceControl`> sub-element in the SqlWorkflowInstanceStore element is omitted, the SqlWorkflowInstanceStore still adds a default control endpoint using the class. + If the `` sub-element in the SqlWorkflowInstanceStore element is omitted, the SqlWorkflowInstanceStore still adds a default control endpoint using the class. ]]> diff --git a/xml/System.ServiceModel.Channels/AsymmetricSecurityBindingElement.xml b/xml/System.ServiceModel.Channels/AsymmetricSecurityBindingElement.xml index 86c7ed048f5..fd4a8fd5956 100644 --- a/xml/System.ServiceModel.Channels/AsymmetricSecurityBindingElement.xml +++ b/xml/System.ServiceModel.Channels/AsymmetricSecurityBindingElement.xml @@ -447,7 +447,7 @@ ## Remarks > [!NOTE] -> If there is nothing in the message that is encrypted, the signature element is not encrypted even when the property is set to . This behavior occurs even with system-provided bindings. However the WSDL generated by WCF still contains the <`sp:EncryptSignature`> assertion. +> If there is nothing in the message that is encrypted, the signature element is not encrypted even when the property is set to . This behavior occurs even with system-provided bindings. However the WSDL generated by WCF still contains the `` assertion. For a listing of the members and their descriptions, see . diff --git a/xml/System.ServiceModel.Channels/MessageHeader.xml b/xml/System.ServiceModel.Channels/MessageHeader.xml index c6303c421c1..482fc84f281 100644 --- a/xml/System.ServiceModel.Channels/MessageHeader.xml +++ b/xml/System.ServiceModel.Channels/MessageHeader.xml @@ -585,7 +585,7 @@ element described in the in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkID=96163). + A reference parameter corresponds to the `` element described in the in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkID=96163). ]]> diff --git a/xml/System.ServiceModel.Channels/MessageHeaderInfo.xml b/xml/System.ServiceModel.Channels/MessageHeaderInfo.xml index 9d40276a2ac..621e032f476 100644 --- a/xml/System.ServiceModel.Channels/MessageHeaderInfo.xml +++ b/xml/System.ServiceModel.Channels/MessageHeaderInfo.xml @@ -135,7 +135,7 @@ element described in the in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkID=96163). + A reference parameter corresponds to the `` element described in the in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkID=96163). ]]> diff --git a/xml/System.ServiceModel.Channels/MessageHeaders.xml b/xml/System.ServiceModel.Channels/MessageHeaders.xml index 8e7b8991d6b..949c5cd149c 100644 --- a/xml/System.ServiceModel.Channels/MessageHeaders.xml +++ b/xml/System.ServiceModel.Channels/MessageHeaders.xml @@ -228,7 +228,7 @@ element described in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkId=96163). + This property corresponds to the `` element described in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkId=96163). @@ -578,7 +578,7 @@ element described in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkId=96163). + This property corresponds to the `` element described in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkId=96163). ]]> @@ -715,7 +715,7 @@ element described in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkId=96163). + This property corresponds to the `` element described in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkId=96163). ]]> @@ -1249,7 +1249,7 @@ element described in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkId=96163). + This property corresponds to the `` element described in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkId=96163). ]]> @@ -1325,7 +1325,7 @@ element described in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkId=96163). + This property corresponds to the `` element described in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkId=96163). ]]> @@ -1436,7 +1436,7 @@ element described in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkId=96163). + This property corresponds to the `` element described in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkId=96163). ]]> @@ -1550,7 +1550,7 @@ element described in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkId=96163). + This property corresponds to the `` element described in the [WS-Addressing specification](https://go.microsoft.com/fwlink/?LinkId=96163). ]]> diff --git a/xml/System.ServiceModel.Channels/SymmetricSecurityBindingElement.xml b/xml/System.ServiceModel.Channels/SymmetricSecurityBindingElement.xml index 438bc074667..4afaf3ed24d 100644 --- a/xml/System.ServiceModel.Channels/SymmetricSecurityBindingElement.xml +++ b/xml/System.ServiceModel.Channels/SymmetricSecurityBindingElement.xml @@ -277,7 +277,7 @@ ## Remarks > [!NOTE] -> If there is nothing in the message that is encrypted, the signature element is not encrypted even when the property is set to . This behavior occurs even with system-provided bindings. However, the WSDL generated by WCF still contains the <`sp:EncryptSignature`> assertion. +> If there is nothing in the message that is encrypted, the signature element is not encrypted even when the property is set to . This behavior occurs even with system-provided bindings. However, the WSDL generated by WCF still contains the `` assertion. For a listing of the members and their descriptions, see . diff --git a/xml/System.ServiceModel.Configuration/BindingElementExtensionElement.xml b/xml/System.ServiceModel.Configuration/BindingElementExtensionElement.xml index 0690f53297f..bb4be218d42 100644 --- a/xml/System.ServiceModel.Configuration/BindingElementExtensionElement.xml +++ b/xml/System.ServiceModel.Configuration/BindingElementExtensionElement.xml @@ -22,7 +22,7 @@ ## Remarks You should derive from the class to use a custom implementation from a machine or application configuration file. - Once a instance has been created, a custom binding element is returned. You can use this in an application configuration file by using the <`add`> element and setting the type attribute to the class, and the name attribute to the custom binding element. + Once a instance has been created, a custom binding element is returned. You can use this in an application configuration file by using the `` element and setting the type attribute to the class, and the name attribute to the custom binding element. ]]> diff --git a/xml/System.ServiceModel.Configuration/ComContractElement.xml b/xml/System.ServiceModel.Configuration/ComContractElement.xml index a785423c016..7b08d2b350a 100644 --- a/xml/System.ServiceModel.Configuration/ComContractElement.xml +++ b/xml/System.ServiceModel.Configuration/ComContractElement.xml @@ -345,11 +345,11 @@ ComSvcConfig.exe /i /application:OnlineStore /contract:ItemOrders.Financial,IFin ## Examples - The following example demonstrates adding two specific UDTs to the <`userDefinedTypes`> section of the configuration file for this purpose. + The following example demonstrates adding two specific UDTs to the `` section of the configuration file for this purpose. [!code-xml[S_UEComContractElement#102](~/samples/snippets/csharp/VS_Snippets_CFX/s_uecomcontractelement/common/app3.config#102)] - The attributes of the <`userDefinedType`> element are defined as follows: + The attributes of the `` element are defined as follows: - `typeName`: An optional attribute that provides the readable type name. This is not used by the runtime but helps a reader to distinguish the types. diff --git a/xml/System.ServiceModel.Configuration/ComUdtElement.xml b/xml/System.ServiceModel.Configuration/ComUdtElement.xml index dae60506d49..1160a859a66 100644 --- a/xml/System.ServiceModel.Configuration/ComUdtElement.xml +++ b/xml/System.ServiceModel.Configuration/ComUdtElement.xml @@ -24,11 +24,11 @@ To circumvent this problem, you can add the UDTs to the configuration file so that they can be included as known types on the appropriate service contract. In order to do so, you have to uniquely identify the UDT and the contract(s), that is, the original COM interface(s) that uses it. - The following example demonstrates adding two specific UDTs to the <`userDefinedTypes`> section of the configuration file for this purpose. + The following example demonstrates adding two specific UDTs to the `` section of the configuration file for this purpose. - The attributes of the <`userDefinedType`> element are defined as follows: + The attributes of the `` element are defined as follows: - `typeName`: an optional attribute that provides the readable type name. This is not used by the runtime but helps a reader to distinguish the types. @@ -43,7 +43,7 @@ ## Examples - The following example demonstrates adding two specific UDTs to the <`userDefinedTypes`> section of the configuration file for this purpose. + The following example demonstrates adding two specific UDTs to the `` section of the configuration file for this purpose. diff --git a/xml/System.ServiceModel.Description/OperationDescription.xml b/xml/System.ServiceModel.Description/OperationDescription.xml index c94de88e848..404543a8093 100644 --- a/xml/System.ServiceModel.Description/OperationDescription.xml +++ b/xml/System.ServiceModel.Description/OperationDescription.xml @@ -575,7 +575,7 @@ property overrides the <`operation`> element name in WSDL. The default operation name is the name of the implementing method. + The property overrides the `` element name in WSDL. The default operation name is the name of the implementing method. ]]> diff --git a/xml/System.ServiceModel.Description/ServiceDescription.xml b/xml/System.ServiceModel.Description/ServiceDescription.xml index 81947a4131a..59b0889eb8d 100644 --- a/xml/System.ServiceModel.Description/ServiceDescription.xml +++ b/xml/System.ServiceModel.Description/ServiceDescription.xml @@ -364,7 +364,7 @@ ## Remarks If the name is `null`, this property returns the name of the service type. If service type is also `null`, it returns the default service name. - When exporting WSDL metadata, the maps to the Web Service Development Language (WSDL) <`service`> element local name part of the (qualified) `name` attribute. + When exporting WSDL metadata, the maps to the Web Service Development Language (WSDL) `` element local name part of the (qualified) `name` attribute. @@ -407,7 +407,7 @@ maps to the Web Service Development Language (WSDL) <`service`> element namespace name part of the (qualified) `name` attribute. + When exporting WSDL metadata, the maps to the Web Service Development Language (WSDL) `` element namespace name part of the (qualified) `name` attribute. diff --git a/xml/System.ServiceModel.Security.Tokens/SecurityContextSecurityToken.xml b/xml/System.ServiceModel.Security.Tokens/SecurityContextSecurityToken.xml index 3ccab51dfbe..3f24907f8e3 100644 --- a/xml/System.ServiceModel.Security.Tokens/SecurityContextSecurityToken.xml +++ b/xml/System.ServiceModel.Security.Tokens/SecurityContextSecurityToken.xml @@ -603,7 +603,7 @@ element. In prior versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], it was emitted as an <`sc:Generation`> element. + Starting with the [!INCLUDE[netfx35_short](~/includes/netfx35-short-md.md)], this property is emitted on the wire as an `` element. In prior versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], it was emitted as an `` element. ]]> diff --git a/xml/System.ServiceModel.Syndication/ResourceCollectionInfo.xml b/xml/System.ServiceModel.Syndication/ResourceCollectionInfo.xml index c145da78a67..0834c40c8dc 100644 --- a/xml/System.ServiceModel.Syndication/ResourceCollectionInfo.xml +++ b/xml/System.ServiceModel.Syndication/ResourceCollectionInfo.xml @@ -178,7 +178,7 @@ elements specify the type of resources that can be added to a collection. + `` elements specify the type of resources that can be added to a collection. ]]> diff --git a/xml/System.ServiceModel.Syndication/SyndicationCategory.xml b/xml/System.ServiceModel.Syndication/SyndicationCategory.xml index dfc6d28ccd6..46b918f23af 100644 --- a/xml/System.ServiceModel.Syndication/SyndicationCategory.xml +++ b/xml/System.ServiceModel.Syndication/SyndicationCategory.xml @@ -379,7 +379,7 @@ is written to the `label` attribute of the <`category`> element. is not serialized to RSS 2.0. + When serialized to Atom 1.0, the is written to the `label` attribute of the `` element. is not serialized to RSS 2.0. @@ -434,7 +434,7 @@ is written to the `term` attribute of the <`category`> element. is not serialized to RSS 2.0. + When serialized to Atom 1.0, the is written to the `term` attribute of the `` element. is not serialized to RSS 2.0. @@ -489,9 +489,9 @@ property is written to the `scheme` attribute of the <`category`> element. + When serialized to Atom 1.0, the property is written to the `scheme` attribute of the `` element. - When serialized to RSS 2.0, the property is written to the `domain` attribute of the <`category`> element. + When serialized to RSS 2.0, the property is written to the `domain` attribute of the `` element. diff --git a/xml/System.ServiceModel.Syndication/SyndicationFeed.xml b/xml/System.ServiceModel.Syndication/SyndicationFeed.xml index 479c7ed1869..a6016ba4701 100644 --- a/xml/System.ServiceModel.Syndication/SyndicationFeed.xml +++ b/xml/System.ServiceModel.Syndication/SyndicationFeed.xml @@ -34,45 +34,45 @@ instance is written to a <`feed`> element. The following table shows how each property defined in the class is serialized to Atom 1.0. + When serialized to Atom 1.0, a instance is written to a `` element. The following table shows how each property defined in the class is serialized to Atom 1.0. |SyndicationFeed property|Serialized form| |------------------------------|---------------------| -|`AttributeExtensions`|An attribute in the <`feed`> element for each attribute in the collection.| -|`Authors`|An <`author`> element for each in the collection.| -|`Categories`|A <`category`> element for each in the collection.| -|`Contributors`|A <`contributor`> element for each in the collection.| -|`Copyright`|A <`rights`> element.| -|`Description`|A <`subtitle`> element.| -|`ElementExtensions`|Each element in the collection is written within the <`feed`> element.| -|`Generator`|A <`generator`> element.| -|`Id`|An <`id`>element.| -|`ImageUri`|A <`logo`> element.| -|`Items`|An <`entry`> element for each in the collection.| +|`AttributeExtensions`|An attribute in the `` element for each attribute in the collection.| +|`Authors`|An `` element for each in the collection.| +|`Categories`|A `` element for each in the collection.| +|`Contributors`|A `` element for each in the collection.| +|`Copyright`|A `` element.| +|`Description`|A `` element.| +|`ElementExtensions`|Each element in the collection is written within the `` element.| +|`Generator`|A `` element.| +|`Id`|An ``element.| +|`ImageUri`|A `` element.| +|`Items`|An `` element for each in the collection.| |`Language`|Not serialized.| -|`LastUpdatedTime`|An <`updated`> element.| -|`Links`|A <`link`> element for each in the collection.| -|`Title`|A <`title`> element.| +|`LastUpdatedTime`|An `` element.| +|`Links`|A `` element for each in the collection.| +|`Title`|A `` element.| - When serialized to RSS 2.0, a <xref:System.ServiceModel.Syndication.SyndicationFeed> instance is written to an <`rss`> element. The following table shows how each property defined in the <xref:System.ServiceModel.Syndication.SyndicationFeed> class is serialized to RSS 2.0. + When serialized to RSS 2.0, a <xref:System.ServiceModel.Syndication.SyndicationFeed> instance is written to an `<rss>` element. The following table shows how each property defined in the <xref:System.ServiceModel.Syndication.SyndicationFeed> class is serialized to RSS 2.0. |SyndicationFeed property|Serialized form| |------------------------------|---------------------| -|`AttributeExtensions`|An attribute in the <`channel`> element for each attribute in the collection.| -|`Authors`|A <`managingEditor`> element if only one <xref:System.ServiceModel.Syndication.SyndicationPerson> is in the collection; otherwise, an <`a10:author`> element for each <xref:System.ServiceModel.Syndication.SyndicationPerson> in the collection.| -|`Categories`|A <`category`> element for each <xref:System.ServiceModel.Syndication.SyndicationCategory> in the collection.| -|`Contributors`|An <`a10:contributor`> element for each <xref:System.ServiceModel.Syndication.SyndicationPerson> in the collection.| -|`Copyright`|A <`copyright`> element.| -|`Description`|A <`description`> element.| -|`ElementExtensions`|Each element in the collection is written within the <`channel`> element.| -|`Generator`|A <`generator`> element.| -|`Id`|An <`a10:id`> element.| -|`ImageUri`|An <`image`> element.| -|`Items`|An <`item`> element for each <xref:System.ServiceModel.Syndication.SyndicationItem> in the collection.| -|`Language`|A <`language`> element.| -|`LastUpdatedTime`|A <`lastBuildDate`> element.| -|`Links`|An <`a10:link`> element for each <xref:System.ServiceModel.Syndication.SyndicationLink> in the collection.| -|`Title`|A <`title`> element.| +|`AttributeExtensions`|An attribute in the `<channel>` element for each attribute in the collection.| +|`Authors`|A `<managingEditor>` element if only one <xref:System.ServiceModel.Syndication.SyndicationPerson> is in the collection; otherwise, an `<a10:author>` element for each <xref:System.ServiceModel.Syndication.SyndicationPerson> in the collection.| +|`Categories`|A `<category>` element for each <xref:System.ServiceModel.Syndication.SyndicationCategory> in the collection.| +|`Contributors`|An `<a10:contributor>` element for each <xref:System.ServiceModel.Syndication.SyndicationPerson> in the collection.| +|`Copyright`|A `<copyright>` element.| +|`Description`|A `<description>` element.| +|`ElementExtensions`|Each element in the collection is written within the `<channel>` element.| +|`Generator`|A `<generator>` element.| +|`Id`|An `<a10:id>` element.| +|`ImageUri`|An `<image>` element.| +|`Items`|An `<item>` element for each <xref:System.ServiceModel.Syndication.SyndicationItem> in the collection.| +|`Language`|A `<language>` element.| +|`LastUpdatedTime`|A `<lastBuildDate>` element.| +|`Links`|An `<a10:link>` element for each <xref:System.ServiceModel.Syndication.SyndicationLink> in the collection.| +|`Title`|A `<title>` element.| @@ -463,7 +463,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - An attribute extension is a valid XML attribute that is not specified in either the Atom 1.0 or RSS 2.0 specifications. When serialized to Atom 1.0, each custom attribute in the collection is written to the <`atom`> element. When serialized to RSS 2.0, each custom attribute is written to the <`channel`> element. For an example of adding an attribute extension, see the [Loosely-Typed Extensions](~/docs/framework/wcf/samples/loosely-typed-extensions-sample.md) sample. + An attribute extension is a valid XML attribute that is not specified in either the Atom 1.0 or RSS 2.0 specifications. When serialized to Atom 1.0, each custom attribute in the collection is written to the `<atom>` element. When serialized to RSS 2.0, each custom attribute is written to the `<channel>` element. For an example of adding an attribute extension, see the [Loosely-Typed Extensions](~/docs/framework/wcf/samples/loosely-typed-extensions-sample.md) sample. @@ -517,7 +517,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - When serialized to Atom 1.0, each <xref:System.ServiceModel.Syndication.SyndicationPerson> in the collection is written to an <`author`> element. When serialized to RSS 2.0, if only a single <xref:System.ServiceModel.Syndication.SyndicationPerson> exists in the collection, it is written to a <`managingEditor`> element. Otherwise, each <xref:System.ServiceModel.Syndication.SyndicationPerson> is written to an <`a10:author`> element. + When serialized to Atom 1.0, each <xref:System.ServiceModel.Syndication.SyndicationPerson> in the collection is written to an `<author>` element. When serialized to RSS 2.0, if only a single <xref:System.ServiceModel.Syndication.SyndicationPerson> exists in the collection, it is written to a `<managingEditor>` element. Otherwise, each <xref:System.ServiceModel.Syndication.SyndicationPerson> is written to an `<a10:author>` element. @@ -620,9 +620,9 @@ <format type="text/markdown"><![CDATA[ ## Remarks - When serialized to Atom 1.0, each <xref:System.ServiceModel.Syndication.SyndicationCategory> in the collection is written to a <`category`> element. + When serialized to Atom 1.0, each <xref:System.ServiceModel.Syndication.SyndicationCategory> in the collection is written to a `<category>` element. - When serialized to RSS 2.0, each <xref:System.ServiceModel.Syndication.SyndicationCategory> in the collection is written to a <`category`> element. + When serialized to RSS 2.0, each <xref:System.ServiceModel.Syndication.SyndicationCategory> in the collection is written to a `<category>` element. @@ -726,9 +726,9 @@ <format type="text/markdown"><![CDATA[ ## Remarks - When serialized to Atom 1.0, each <xref:System.ServiceModel.Syndication.SyndicationPerson> in the collection is written to a <`contributor`> element. + When serialized to Atom 1.0, each <xref:System.ServiceModel.Syndication.SyndicationPerson> in the collection is written to a `<contributor>` element. - When serialized to RSS 2.0, each <xref:System.ServiceModel.Syndication.SyndicationPerson> in the collection is written to an <`a10:contributor`> element. + When serialized to RSS 2.0, each <xref:System.ServiceModel.Syndication.SyndicationPerson> in the collection is written to an `<a10:contributor>` element. @@ -790,9 +790,9 @@ <format type="text/markdown"><![CDATA[ ## Remarks - When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Copyright%2A> is written to a <`rights`> element. + When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Copyright%2A> is written to a `<rights>` element. - When serialized to RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Copyright%2A> is written to a <`copyright`> element. + When serialized to RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Copyright%2A> is written to a `<copyright>` element. @@ -1014,9 +1014,9 @@ <format type="text/markdown"><![CDATA[ ## Remarks - When serialized to Atom 1.0, <xref:System.ServiceModel.Syndication.SyndicationFeed.Description%2A> is written to a <`subtitle`> element. + When serialized to Atom 1.0, <xref:System.ServiceModel.Syndication.SyndicationFeed.Description%2A> is written to a `<subtitle>` element. - When serialized to RSS 2.0, <xref:System.ServiceModel.Syndication.SyndicationFeed.Description%2A> is written to a <`description`> element. + When serialized to RSS 2.0, <xref:System.ServiceModel.Syndication.SyndicationFeed.Description%2A> is written to a `<description>` element. @@ -1159,7 +1159,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - When serialized to Atom 1.0 and RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Generator%2A> is written to a <`generator`> element. + When serialized to Atom 1.0 and RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Generator%2A> is written to a `<generator>` element. @@ -1338,9 +1338,9 @@ <format type="text/markdown"><![CDATA[ ## Remarks - When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Id%2A> is written to an <`id`> element. + When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Id%2A> is written to an `<id>` element. - When serialized to RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Id%2A> is written to an <`a10:id`> element. + When serialized to RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Id%2A> is written to an `<a10:id>` element. @@ -1402,9 +1402,9 @@ <format type="text/markdown"><![CDATA[ ## Remarks - When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.ImageUrl%2A> property is written to a <`logo`> element. + When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.ImageUrl%2A> property is written to a `<logo>` element. - When serialized to RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.ImageUrl%2A> property is written to an <`image`> element. + When serialized to RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.ImageUrl%2A> property is written to an `<image>` element. @@ -1458,9 +1458,9 @@ <format type="text/markdown"><![CDATA[ ## Remarks - When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Items%2A> collection is written to <`entry`> elements. + When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Items%2A> collection is written to `<entry>` elements. - When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Items%2A> collection is written to <`item`> elements. + When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Items%2A> collection is written to `<item>` elements. @@ -1522,9 +1522,9 @@ <format type="text/markdown"><![CDATA[ ## Remarks - When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Language%2A> property is written to the `lang` attribute in the <`feed`> element. + When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Language%2A> property is written to the `lang` attribute in the `<feed>` element. - When serialized to RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Language%2A> property is written to the <`language`> element. + When serialized to RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Language%2A> property is written to the `<language>` element. @@ -1586,9 +1586,9 @@ <format type="text/markdown"><![CDATA[ ## Remarks - When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.LastUpdatedTime%2A> property is written to an <`updated`>element. + When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.LastUpdatedTime%2A> property is written to an `<updated>`element. - When serialized to RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.LastUpdatedTime%2A> property is written to a <`lastBuildDate`> element. + When serialized to RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.LastUpdatedTime%2A> property is written to a `<lastBuildDate>` element. @@ -1642,9 +1642,9 @@ <format type="text/markdown"><![CDATA[ ## Remarks - When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Links%2A> collection is written to a number of <`link`> elements. + When serialized to Atom 1.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Links%2A> collection is written to a number of `<link>` elements. - When serialized to RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Links%2A> collection is written to a number of <`a10:link`> elements. + When serialized to RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Links%2A> collection is written to a number of `<a10:link>` elements. @@ -2016,7 +2016,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - When serialized to Atom 1.0 and RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Title%2A> property is written to a <`title`> element. + When serialized to Atom 1.0 and RSS 2.0, the <xref:System.ServiceModel.Syndication.SyndicationFeed.Title%2A> property is written to a `<title>` element. @@ -2082,7 +2082,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - Attribute extensions are custom attributes that are not defined by the Atom 1.0 or RSS 2.0 specifications. They are serialized as an attribute of the <`feed`> (for Atom 1.0) or <`rss`> (for RSS 1.0) element, which depends upon the syndication version being used. This method is an extension point that allows you to handle the deserialization of a custom attribute extension. To do this, you must derive a class from <xref:System.ServiceModel.Syndication.SyndicationFeed> and override this method. This method is called for all unrecognized attribute extensions. + Attribute extensions are custom attributes that are not defined by the Atom 1.0 or RSS 2.0 specifications. They are serialized as an attribute of the `<feed>` (for Atom 1.0) or `<rss>` (for RSS 1.0) element, which depends upon the syndication version being used. This method is an extension point that allows you to handle the deserialization of a custom attribute extension. To do this, you must derive a class from <xref:System.ServiceModel.Syndication.SyndicationFeed> and override this method. This method is called for all unrecognized attribute extensions. ]]></format> </remarks> @@ -2171,7 +2171,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - Attribute extensions are custom attributes that are not defined by the Atom 1.0 or RSS 2.0 specifications. They are serialized as an attribute of the <`feed`> (for Atom 1.0) or <`rss`> (for RSS 1.0) element, which depends upon the syndication version being used. This method is an extension point that allows you to handle the serialization of custom attribute extensions. To do this, you must derive a class from <xref:System.ServiceModel.Syndication.SyndicationFeed> and override this method. This method is called for all unrecognized attribute extensions. + Attribute extensions are custom attributes that are not defined by the Atom 1.0 or RSS 2.0 specifications. They are serialized as an attribute of the `<feed>` (for Atom 1.0) or `<rss>` (for RSS 1.0) element, which depends upon the syndication version being used. This method is an extension point that allows you to handle the serialization of custom attribute extensions. To do this, you must derive a class from <xref:System.ServiceModel.Syndication.SyndicationFeed> and override this method. This method is called for all unrecognized attribute extensions. ]]></format> </remarks> diff --git a/xml/System.ServiceModel.Syndication/SyndicationLink.xml b/xml/System.ServiceModel.Syndication/SyndicationLink.xml index cc3636241e9..b62643a6b53 100644 --- a/xml/System.ServiceModel.Syndication/SyndicationLink.xml +++ b/xml/System.ServiceModel.Syndication/SyndicationLink.xml @@ -1023,7 +1023,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - Attribute extensions are custom attributes that are not defined by the Atom 1.0 or RSS 2.0 specifications. They are serialized as an attribute of the `<link`> element. This method is an extension point that allows you to handle the deserialization of a custom attribute extension. To do this, you must derive a class from <xref:System.ServiceModel.Syndication.SyndicationLink> and override this method. This method is called for all unrecognized attribute extensions. + Attribute extensions are custom attributes that are not defined by the Atom 1.0 or RSS 2.0 specifications. They are serialized as an attribute of the `<link>` element. This method is an extension point that allows you to handle the deserialization of a custom attribute extension. To do this, you must derive a class from <xref:System.ServiceModel.Syndication.SyndicationLink> and override this method. This method is called for all unrecognized attribute extensions. ]]></format> </remarks> diff --git a/xml/System.ServiceModel.Syndication/Workspace.xml b/xml/System.ServiceModel.Syndication/Workspace.xml index 49265ed77ee..715807eb5b8 100644 --- a/xml/System.ServiceModel.Syndication/Workspace.xml +++ b/xml/System.ServiceModel.Syndication/Workspace.xml @@ -174,7 +174,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - An attribute extension is a valid XML attribute that is not specified in either the Atom 1.0 or RSS 2.0 specifications. When serialized to Atom 1.0, each custom attribute in the collection is written to the <`atom`> element. When serialized to RSS 2.0, each custom attribute is written to the <`channel`> element. + An attribute extension is a valid XML attribute that is not specified in either the Atom 1.0 or RSS 2.0 specifications. When serialized to Atom 1.0, each custom attribute in the collection is written to the `<atom>` element. When serialized to RSS 2.0, each custom attribute is written to the `<channel>` element. ]]></format> </remarks> diff --git a/xml/System.ServiceModel/OperationContractAttribute.xml b/xml/System.ServiceModel/OperationContractAttribute.xml index 84c77316f41..5e81c63a36f 100644 --- a/xml/System.ServiceModel/OperationContractAttribute.xml +++ b/xml/System.ServiceModel/OperationContractAttribute.xml @@ -654,7 +654,7 @@ public class InitializeAndTerminateService <format type="text/markdown"><![CDATA[ ## Remarks - Use the <xref:System.ServiceModel.OperationContractAttribute.Name%2A> property to override the <`operation`> element name in WSDL. The default operation name is the name of the implementing method. + Use the <xref:System.ServiceModel.OperationContractAttribute.Name%2A> property to override the `<operation>` element name in WSDL. The default operation name is the name of the implementing method. diff --git a/xml/System.Web.Compilation/ConnectionStringsExpressionBuilder.xml b/xml/System.Web.Compilation/ConnectionStringsExpressionBuilder.xml index 906d5252c96..d99a20c1470 100644 --- a/xml/System.Web.Compilation/ConnectionStringsExpressionBuilder.xml +++ b/xml/System.Web.Compilation/ConnectionStringsExpressionBuilder.xml @@ -31,7 +31,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - The <xref:System.Web.Compilation.ConnectionStringsExpressionBuilder> class provides access to values in the <`connectionStrings`> section of the Web.config file. The <`connectionStrings`> section of the Web.config file contains connection string values in name/value pairs. + The <xref:System.Web.Compilation.ConnectionStringsExpressionBuilder> class provides access to values in the `<connectionStrings>` section of the Web.config file. The `<connectionStrings>` section of the Web.config file contains connection string values in name/value pairs. A connection string value is retrieved by assigning an expression of the form @@ -143,7 +143,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - This method is called when an expression of the form `<%$ ConnectionStrings: secureConnectionString %>` is encountered in a page that is not compiled. It retrieves the appropriate value from the <`connectionStrings`> section of the Web.config file. This method overrides the <xref:System.Web.Compilation.ExpressionBuilder.EvaluateExpression%2A> method by calling the <xref:System.Web.Compilation.ConnectionStringsExpressionBuilder.GetConnectionString%2A> method if a connection string is included in the `parsedData` parameter, or by calling the <xref:System.Web.Compilation.ConnectionStringsExpressionBuilder.GetConnectionStringProviderName%2A> method if a connection string is not included in the `parsedData` parameter. + This method is called when an expression of the form `<%$ ConnectionStrings: secureConnectionString %>` is encountered in a page that is not compiled. It retrieves the appropriate value from the `<connectionStrings>` section of the Web.config file. This method overrides the <xref:System.Web.Compilation.ExpressionBuilder.EvaluateExpression%2A> method by calling the <xref:System.Web.Compilation.ConnectionStringsExpressionBuilder.GetConnectionString%2A> method if a connection string is included in the `parsedData` parameter, or by calling the <xref:System.Web.Compilation.ConnectionStringsExpressionBuilder.GetConnectionStringProviderName%2A> method if a connection string is not included in the `parsedData` parameter. ]]></format> </remarks> diff --git a/xml/System.Web.Configuration/NamespaceInfo.xml b/xml/System.Web.Configuration/NamespaceInfo.xml index 584a6d74dd0..66ef9952ea7 100644 --- a/xml/System.Web.Configuration/NamespaceInfo.xml +++ b/xml/System.Web.Configuration/NamespaceInfo.xml @@ -20,7 +20,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - The <xref:System.Web.Configuration.NamespaceCollection> contains <xref:System.Web.Configuration.NamespaceInfo> objects, which correspond to the `add` elements within the `namespaces` section. Each <xref:System.Web.Configuration.NamespaceInfo> object is the same as an `Import` (<`%@ Import %`>) directive that applies to all pages and controls in the scope of the configuration file. The `Import` directive allows you to import a namespace into your ASP.NET page, making all its classes available for use on your page. + The <xref:System.Web.Configuration.NamespaceCollection> contains <xref:System.Web.Configuration.NamespaceInfo> objects, which correspond to the `add` elements within the `namespaces` section. Each <xref:System.Web.Configuration.NamespaceInfo> object is the same as an `Import` (`<%@ Import %>`) directive that applies to all pages and controls in the scope of the configuration file. The `Import` directive allows you to import a namespace into your ASP.NET page, making all its classes available for use on your page. diff --git a/xml/System.Web.UI.MobileControls/DeviceSpecificChoice.xml b/xml/System.Web.UI.MobileControls/DeviceSpecificChoice.xml index d33d27eee4f..1b9577409cd 100644 --- a/xml/System.Web.UI.MobileControls/DeviceSpecificChoice.xml +++ b/xml/System.Web.UI.MobileControls/DeviceSpecificChoice.xml @@ -227,7 +227,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - The filter name must be the name of a method on the page, in the associated `.ascx` file, or the name of a valid device filter defined in the <`deviceFilters`> section of Web.config. If a method name is specified with the <xref:System.Web.UI.MobileControls.DeviceSpecificChoice.Filter%2A> property, that method must match the following prototype. + The filter name must be the name of a method on the page, in the associated `.ascx` file, or the name of a valid device filter defined in the `<deviceFilters>` section of Web.config. If a method name is specified with the <xref:System.Web.UI.MobileControls.DeviceSpecificChoice.Filter%2A> property, that method must match the following prototype. ``` public bool methodName(System.Web.Mobile.MobileCapabilities @@ -241,7 +241,7 @@ public bool myChoiceMethod(System.Web.Mobile.MobileCapabilities capabilities, String optionalArgument); ``` - When evaluating the [\<Choice>](https://msdn.microsoft.com/library/c81bee77-bb45-4211-be0f-e13a040b3c2d) element, a check is made to determine whether a method of the appropriate signature exists on the page. If not, ASP.NET checks the <`deviceFilters`> section of Web.config. + When evaluating the [\<Choice>](https://msdn.microsoft.com/library/c81bee77-bb45-4211-be0f-e13a040b3c2d) element, a check is made to determine whether a method of the appropriate signature exists on the page. If not, ASP.NET checks the `<deviceFilters>` section of Web.config. > [!NOTE] > Device filters are case-sensitive. diff --git a/xml/System.Web.UI.MobileControls/FormControlBuilder.xml b/xml/System.Web.UI.MobileControls/FormControlBuilder.xml index 0524441d7cc..5d7889402d8 100644 --- a/xml/System.Web.UI.MobileControls/FormControlBuilder.xml +++ b/xml/System.Web.UI.MobileControls/FormControlBuilder.xml @@ -26,7 +26,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - The <xref:System.Web.UI.MobileControls.FormControlBuilder> class parses literal text. It is internally created and used by the page parser when parsing a <`mobile:Form`> tag. + The <xref:System.Web.UI.MobileControls.FormControlBuilder> class parses literal text. It is internally created and used by the page parser when parsing a `<mobile:Form>` tag. ]]></format> </remarks> diff --git a/xml/System.Web.UI.MobileControls/LiteralText.xml b/xml/System.Web.UI.MobileControls/LiteralText.xml index 823a68d6243..614e22053b6 100644 --- a/xml/System.Web.UI.MobileControls/LiteralText.xml +++ b/xml/System.Web.UI.MobileControls/LiteralText.xml @@ -40,7 +40,7 @@ - The control renders literal text on its own line with the appropriate style attributes applied. -- When nesting tags, the hyperlink tag (anchor tag: <`a`>) does not recognize nested tags. For example, nesting the <`b`> or <`i`> tag as literal text inside the <`a`> tag will not render a link as bold or italic. The control completely ignores all tags inside of the <`a`> tag. +- When nesting tags, the hyperlink tag (anchor tag: `<a>`) does not recognize nested tags. For example, nesting the `<b>` or `<i>` tag as literal text inside the `<a>` tag will not render a link as bold or italic. The control completely ignores all tags inside of the `<a>` tag. > [!NOTE] > It is important for an adapter to use the <xref:System.Web.UI.MobileControls.TextView.Text%2A?displayProperty=nameWithType> property to dynamically set the text that you want to display on a form. Do not use this class to do so. diff --git a/xml/System.Web.UI.MobileControls/MobilePage.xml b/xml/System.Web.UI.MobileControls/MobilePage.xml index 69a15831d46..24fc739adad 100644 --- a/xml/System.Web.UI.MobileControls/MobilePage.xml +++ b/xml/System.Web.UI.MobileControls/MobilePage.xml @@ -317,7 +317,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - In addition to the <xref:System.Web.UI.IAttributeAccessor> interface, the ASP.NET page framework provides a `CustomAttributes` dictionary that allows you to specify additional attributes, enable or disable custom attributing, or adjust a control's behavior or rendering. To enable or disable custom attributing, you can either set the <xref:System.Web.UI.MobileControls.MobilePage.AllowCustomAttributes%2A> property to `true`, or you can set the `allowCustomAttributes` attribute of the <`mobileControls`> section of Web.config to `true`. + In addition to the <xref:System.Web.UI.IAttributeAccessor> interface, the ASP.NET page framework provides a `CustomAttributes` dictionary that allows you to specify additional attributes, enable or disable custom attributing, or adjust a control's behavior or rendering. To enable or disable custom attributing, you can either set the <xref:System.Web.UI.MobileControls.MobilePage.AllowCustomAttributes%2A> property to `true`, or you can set the `allowCustomAttributes` attribute of the `<mobileControls>` section of Web.config to `true`. > [!NOTE] > When custom attributes are enabled, typographic errors in property names can be interpreted as custom attributes. For example, if a developer incorrectly specifies the <xref:System.Web.UI.MobileControls.TextControl.Text%2A> property of a control as "Txet", the parser would save it as a custom attribute called "Txet" instead of raising an exception. For this reason, custom attributes are disabled by default. diff --git a/xml/System.Web.UI.WebControls.WebParts/ConnectionsZone.xml b/xml/System.Web.UI.WebControls.WebParts/ConnectionsZone.xml index 673e1856eb2..7d3ed68b5ab 100644 --- a/xml/System.Web.UI.WebControls.WebParts/ConnectionsZone.xml +++ b/xml/System.Web.UI.WebControls.WebParts/ConnectionsZone.xml @@ -83,7 +83,7 @@ [!code-csharp[WebParts_ConnectionZone_Overview#2](~/samples/snippets/csharp/VS_Snippets_WebNet/WebParts_ConnectionZone_Overview/CS/ZipCodeComponent.cs#2)] [!code-vb[WebParts_ConnectionZone_Overview#2](~/samples/snippets/visualbasic/VS_Snippets_WebNet/WebParts_ConnectionZone_Overview/VB/ZipCodeComponent.vb#2)] - The third part of the example code is the Web page. Near the top are `Register` directives for the user control and the custom controls used in the connection. An <`asp:connectionszone>` element is declared in the page as an example of using the <xref:System.Web.UI.WebControls.WebParts.ConnectionsZone> control declaratively. Within the element, a number of properties are set declaratively. Other properties on the connections zone are set programmatically in the `<script>` section of the page. + The third part of the example code is the Web page. Near the top are `Register` directives for the user control and the custom controls used in the connection. An `<asp:connectionszone>` element is declared in the page as an example of using the <xref:System.Web.UI.WebControls.WebParts.ConnectionsZone> control declaratively. Within the element, a number of properties are set declaratively. Other properties on the connections zone are set programmatically in the `<script>` section of the page. [!code-aspx-csharp[WebParts_ConnectionZone_Overview#1](~/samples/snippets/csharp/VS_Snippets_WebNet/WebParts_ConnectionZone_Overview/CS/connectionZoneCS.aspx#1)] [!code-aspx-vb[WebParts_ConnectionZone_Overview#1](~/samples/snippets/visualbasic/VS_Snippets_WebNet/WebParts_ConnectionZone_Overview/VB/connectionZoneVB.aspx#1)] diff --git a/xml/System.Web.UI.WebControls.WebParts/ProxyWebPartManager.xml b/xml/System.Web.UI.WebControls.WebParts/ProxyWebPartManager.xml index 7aed76219bb..d66312a49c8 100644 --- a/xml/System.Web.UI.WebControls.WebParts/ProxyWebPartManager.xml +++ b/xml/System.Web.UI.WebControls.WebParts/ProxyWebPartManager.xml @@ -42,7 +42,7 @@ ## Remarks The <xref:System.Web.UI.WebControls.WebParts.ProxyWebPartManager> control exists for the particular scenario of declaring static connections in content pages when a <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control has already been declared in a master page. - By design, a Web page that uses Web Parts controls must contain one (and only one) <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control that manages all Web Parts controls on the page. When a Web Parts application uses master pages, it is common to place the <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control in the master page, because all the content pages are merged with the master page at run time and the single <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control will manage all the Web Parts controls from all content pages. However, when developers want to declare static connections in the content pages of such an application, they might seem to face a limitation. A static Web Parts connection can be declared only by adding an <`asp:webpartconnection>` element as a child of a `<staticconnections>` element, which itself must be a child of a `<asp:webpartmanager>` element. But because the <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control was already declared in the master page, and is the one permitted <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control, developers cannot declare additional <xref:System.Web.UI.WebControls.WebParts.WebPartManager> controls in the content pages to add static connections. + By design, a Web page that uses Web Parts controls must contain one (and only one) <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control that manages all Web Parts controls on the page. When a Web Parts application uses master pages, it is common to place the <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control in the master page, because all the content pages are merged with the master page at run time and the single <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control will manage all the Web Parts controls from all content pages. However, when developers want to declare static connections in the content pages of such an application, they might seem to face a limitation. A static Web Parts connection can be declared only by adding an `<asp:webpartconnection>` element as a child of a `<staticconnections>` element, which itself must be a child of a `<asp:webpartmanager>` element. But because the <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control was already declared in the master page, and is the one permitted <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control, developers cannot declare additional <xref:System.Web.UI.WebControls.WebParts.WebPartManager> controls in the content pages to add static connections. The <xref:System.Web.UI.WebControls.WebParts.ProxyWebPartManager> control takes the place of the <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control in this scenario. Developers declare an `<asp:proxywebpartmanager>` element instead of an `<asp:webpartmanager>` element in their content pages, and can then declare static connections as child elements. At run time, the connections in the <xref:System.Web.UI.WebControls.WebParts.ProxyWebPartManager> control are simply added to the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.StaticConnections%2A> collection of the <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control and treated like any other connection. @@ -82,7 +82,7 @@ [!code-aspx-csharp[WebParts_ProxyWebPartManager_Overview#1](~/samples/snippets/csharp/VS_Snippets_WebNet/WebParts_ProxyWebPartManager_Overview/CS/MasterPageCS.master#1)] [!code-aspx-vb[WebParts_ProxyWebPartManager_Overview#1](~/samples/snippets/visualbasic/VS_Snippets_WebNet/WebParts_ProxyWebPartManager_Overview/VB/MasterPageVB.master#1)] - The fourth part of the code example is the content page. You should copy the following source code and save it in a file with an .aspx extension. Notice that its `Page` directive contains a `MasterFile` attribute to refer to the master page. Also, this page has a `Register` directive to register the file in the App_Code folder that contains the dynamically compiled custom <xref:System.Web.UI.WebControls.WebParts.WebPart> controls that participate in the connection. Within the `<asp:content>` tags of the page, there is an <`asp:proxywebpartmanager>` element, with a child `<staticconnections>` element, which in turn has a child `<asp:webpartconnection>` element to declare the details of the connection. Within the `<script>` tags on the page, the `Button1_Click` method adds some code that accesses the main <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control in the master page and the <xref:System.Web.UI.WebControls.WebParts.ProxyWebPartManager> control in the content page, and writes some of their details to the page. + The fourth part of the code example is the content page. You should copy the following source code and save it in a file with an .aspx extension. Notice that its `Page` directive contains a `MasterFile` attribute to refer to the master page. Also, this page has a `Register` directive to register the file in the App_Code folder that contains the dynamically compiled custom <xref:System.Web.UI.WebControls.WebParts.WebPart> controls that participate in the connection. Within the `<asp:content>` tags of the page, there is an `<asp:proxywebpartmanager>` element, with a child `<staticconnections>` element, which in turn has a child `<asp:webpartconnection>` element to declare the details of the connection. Within the `<script>` tags on the page, the `Button1_Click` method adds some code that accesses the main <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control in the master page and the <xref:System.Web.UI.WebControls.WebParts.ProxyWebPartManager> control in the content page, and writes some of their details to the page. [!code-aspx-csharp[WebParts_ProxyWebPartManager_Overview#2](~/samples/snippets/csharp/VS_Snippets_WebNet/WebParts_ProxyWebPartManager_Overview/CS/contentPage1CS.aspx#2)] [!code-aspx-vb[WebParts_ProxyWebPartManager_Overview#2](~/samples/snippets/visualbasic/VS_Snippets_WebNet/WebParts_ProxyWebPartManager_Overview/VB/contentPage1VB.aspx#2)] diff --git a/xml/System.Web.UI.WebControls.WebParts/WebPartConnection.xml b/xml/System.Web.UI.WebControls.WebParts/WebPartConnection.xml index 8519d122fd4..3818e8ed462 100644 --- a/xml/System.Web.UI.WebControls.WebParts/WebPartConnection.xml +++ b/xml/System.Web.UI.WebControls.WebParts/WebPartConnection.xml @@ -79,7 +79,7 @@ The third part of the code example is the Web page. Near the top are the `Register` directives for the user control and the custom <xref:System.Web.UI.WebControls.WebParts.WebPart> controls. Because the example assumes dynamic compilation of the controls, the source code for the controls should be in an App_Code subfolder; the `Register` tag in the page references only an arbitrary tag prefix and the namespace of the controls. The custom <xref:System.Web.UI.WebControls.WebParts.WebPart> controls (the provider and consumer) are declared within the Web page's `<asp:webpartzone>` element, inside a `<zonetemplate>` element. - The page provides three ways to form a connection between the custom controls. The first method is declarative. In the markup for the page, a <`StaticConnections>` element is declared, and within that is an `<asp:WebPartConnections>` element, with the various consumer and provider details of the connection specified as attributes. This is one way to create a connection, by declaring it directly in the Web page, specifically within the `<asp:WebPartManager>` element. Because of this static connection, a connection between the two custom controls is created immediately the first time the page loads. + The page provides three ways to form a connection between the custom controls. The first method is declarative. In the markup for the page, a `<StaticConnections>` element is declared, and within that is an `<asp:WebPartConnections>` element, with the various consumer and provider details of the connection specified as attributes. This is one way to create a connection, by declaring it directly in the Web page, specifically within the `<asp:WebPartManager>` element. Because of this static connection, a connection between the two custom controls is created immediately the first time the page loads. A second method for forming a connection between the controls is provided by the `<asp:connectionszone>` element in the page. If a user switches a page into connect display mode at run time, and clicks a connect verb on one of the custom controls, the `<asp:connectionszone>` element automatically renders the UI for creating a connection. diff --git a/xml/System.Web.UI.WebControls.WebParts/WebPartManager.xml b/xml/System.Web.UI.WebControls.WebParts/WebPartManager.xml index 26fff0e621e..4aab8314f82 100644 --- a/xml/System.Web.UI.WebControls.WebParts/WebPartManager.xml +++ b/xml/System.Web.UI.WebControls.WebParts/WebPartManager.xml @@ -856,7 +856,7 @@ [!code-csharp[WebParts_WebPartManager_CloseWebPart#3](~/samples/snippets/csharp/VS_Snippets_WebNet/WebParts_WebPartManager_CloseWebPart/CS/textdisplaywebpart.cs#3)] [!code-vb[WebParts_WebPartManager_CloseWebPart#3](~/samples/snippets/visualbasic/VS_Snippets_WebNet/WebParts_WebPartManager_CloseWebPart/VB/textdisplaywebpart.vb#3)] - The third part of the code example is the Web page. The page contains a <xref:System.Web.UI.WebControls.WebParts.CatalogZone> zone, with an <`asp:pagecatalogpart>` element declared within it. This is what will contain the closed <xref:System.Web.UI.WebControls.WebParts.WebPart> control and enable users to add it back to the page. The `Button1_Click` method directly calls the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.CloseWebPart%2A> method to close the custom <xref:System.Web.UI.WebControls.WebParts.WebPart> control, although a user can also close the control through the verbs menu. + The third part of the code example is the Web page. The page contains a <xref:System.Web.UI.WebControls.WebParts.CatalogZone> zone, with an `<asp:pagecatalogpart>` element declared within it. This is what will contain the closed <xref:System.Web.UI.WebControls.WebParts.WebPart> control and enable users to add it back to the page. The `Button1_Click` method directly calls the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.CloseWebPart%2A> method to close the custom <xref:System.Web.UI.WebControls.WebParts.WebPart> control, although a user can also close the control through the verbs menu. [!code-aspx-csharp[WebParts_WebPartManager_CloseWebPart#1](~/samples/snippets/csharp/VS_Snippets_WebNet/WebParts_WebPartManager_CloseWebPart/CS/closeWebPartCS.aspx#1)] [!code-aspx-vb[WebParts_WebPartManager_CloseWebPart#1](~/samples/snippets/visualbasic/VS_Snippets_WebNet/WebParts_WebPartManager_CloseWebPart/VB/closeWebPartVB.aspx#1)] @@ -3895,7 +3895,7 @@ protected void mgr1_AuthorizeWebPart(object sender, ## Remarks The <xref:System.Web.UI.WebControls.WebParts.WebPartManager.OnWebPartAdded%2A> method is called during the process of adding a <xref:System.Web.UI.WebControls.WebParts.WebPart> control (or other server control that is added to a <xref:System.Web.UI.WebControls.WebParts.WebPartZoneBase> zone) to a page. - Page developers can create a custom handler for the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.WebPartAdded> event by adding the `OnWebPartAdded` attribute to the <`asp:webpartmanager>` element, and assigning a custom method name to the attribute. + Page developers can create a custom handler for the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.WebPartAdded> event by adding the `OnWebPartAdded` attribute to the `<asp:webpartmanager>` element, and assigning a custom method name to the attribute. ]]></format> </remarks> @@ -4052,7 +4052,7 @@ protected void mgr1_AuthorizeWebPart(object sender, ## Remarks The <xref:System.Web.UI.WebControls.WebParts.WebPartManager.OnWebPartDeleted%2A> method is called during the process of deleting a <xref:System.Web.UI.WebControls.WebParts.WebPart> control (or other server control that is added to a <xref:System.Web.UI.WebControls.WebParts.WebPartZoneBase> zone) from a page. - Page developers can create a custom handler for the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.WebPartDeleted> event by adding the `OnWebPartDeleted` attribute to the <`asp:webpartmanager>` element, and assigning a custom method name to the attribute. + Page developers can create a custom handler for the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.WebPartDeleted> event by adding the `OnWebPartDeleted` attribute to the `<asp:webpartmanager>` element, and assigning a custom method name to the attribute. ]]></format> </remarks> @@ -4133,7 +4133,7 @@ protected void mgr1_AuthorizeWebPart(object sender, The <xref:System.Web.UI.WebControls.WebParts.WebPartManager.WebPartMoved> event is raised when a control is moved within its current zone, or to another zone, and it does not matter whether the movement is done programmatically or by a user dragging the control. - Page developers can create a custom handler for the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.WebPartMoved> event by adding the `OnWebPartMoved` attribute to the <`asp:webpartmanager>` element, and assigning a custom method name to the attribute. + Page developers can create a custom handler for the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.WebPartMoved> event by adding the `OnWebPartMoved` attribute to the `<asp:webpartmanager>` element, and assigning a custom method name to the attribute. ]]></format> </remarks> @@ -4212,7 +4212,7 @@ protected void mgr1_AuthorizeWebPart(object sender, The method provides programmatic control over the process of creating connections, and the associated event is a convenient point at which to update the user interface (UI) or notify a user that a connection has been established. - Page developers can create a custom handler for the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.WebPartsConnected> event by adding the `OnWebPartsConnected` attribute to the <`asp:webpartmanager>` element, and assigning a custom method name to the attribute. + Page developers can create a custom handler for the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.WebPartsConnected> event by adding the `OnWebPartsConnected` attribute to the `<asp:webpartmanager>` element, and assigning a custom method name to the attribute. ]]></format> </remarks> @@ -4291,7 +4291,7 @@ protected void mgr1_AuthorizeWebPart(object sender, The method provides programmatic control over the process of ending a connection, so that developers can inform the user, make changes to the user interface (UI), or make other changes to the application. - Page developers can create a custom handler for the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.WebPartsDisconnected> event by adding the `OnWebPartsDisconnected` attribute to the <`asp:webpartmanager>` element, and assigning a custom method name to the attribute. + Page developers can create a custom handler for the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.WebPartsDisconnected> event by adding the `OnWebPartsDisconnected` attribute to the `<asp:webpartmanager>` element, and assigning a custom method name to the attribute. ]]></format> </remarks> @@ -5301,7 +5301,7 @@ protected void mgr1_AuthorizeWebPart(object sender, ## Remarks The <xref:System.Web.UI.WebControls.WebParts.WebPartManager.WebPartClosing> event is raised by the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.OnWebPartClosing%2A> method when the <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control is in the process of closing a control. If the removal of the control is successful, this event is followed by the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.WebPartClosed> event. - Page developers can provide a custom handler for the event by adding the `OnWebPartClosed` attribute to the <`asp:webpartmanager>` element in a page, and assigning a custom method name to the attribute. + Page developers can provide a custom handler for the event by adding the `OnWebPartClosed` attribute to the `<asp:webpartmanager>` element in a page, and assigning a custom method name to the attribute. Normally, when the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.WebPartClosing> event is raised as a direct result of a user closing a <xref:System.Web.UI.WebControls.WebParts.WebPart> control, the event can be cancelled. However, there is a scenario in which the event cannot be cancelled. If a <xref:System.Web.UI.WebControls.WebParts.WebPartZone> control is deleted, the <xref:System.Web.UI.WebControls.WebParts.WebPart> controls it contains must all be closed, otherwise they would be orphaned. In this case the <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control closes the <xref:System.Web.UI.WebControls.WebParts.WebPart> controls, not the user. And when the <xref:System.Web.UI.WebControls.WebParts.WebPartManager> control is in the process of calling the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.CloseWebPart%2A> method to close each control, and the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.WebPartClosing> event is raised, the event cannot be cancelled (by design) because the <xref:System.Web.UI.WebControls.WebParts.WebPartManager> needs to complete the task of cleaning up all the zone's controls. diff --git a/xml/System.Web.UI.WebControls/PasswordRecovery.xml b/xml/System.Web.UI.WebControls/PasswordRecovery.xml index 85c3b9dafb6..49cee55c7ec 100644 --- a/xml/System.Web.UI.WebControls/PasswordRecovery.xml +++ b/xml/System.Web.UI.WebControls/PasswordRecovery.xml @@ -1260,7 +1260,7 @@ ## Remarks The <xref:System.Web.UI.WebControls.PasswordRecovery.MembershipProvider%2A> property identifies the membership provider used to verify user information entered in the <xref:System.Web.UI.WebControls.PasswordRecovery> control. - Membership providers are defined in the Web.config file in the <`membership`> section. + Membership providers are defined in the Web.config file in the `<membership>` section. Setting the <xref:System.Web.UI.WebControls.PasswordRecovery.MembershipProvider%2A> property will change the provider used. If you do not set the <xref:System.Web.UI.WebControls.PasswordRecovery.MembershipProvider%2A> property, it will always return <xref:System.String.Empty>. diff --git a/xml/System.Workflow.Activities/WorkflowServiceAttributes.xml b/xml/System.Workflow.Activities/WorkflowServiceAttributes.xml index 03a75fe78ba..03c2da7f92f 100644 --- a/xml/System.Workflow.Activities/WorkflowServiceAttributes.xml +++ b/xml/System.Workflow.Activities/WorkflowServiceAttributes.xml @@ -329,7 +329,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - This property corresponds to the <`wsdl:service`> element when exported. The default value is null. + This property corresponds to the `<wsdl:service>` element when exported. The default value is null. @@ -371,7 +371,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - This value corresponds to the value of the `targetNamespace` attribute for the <`wsdl:definitions`> element that contains the <`wsdl:service`> element when exported. The default value is null. + This value corresponds to the value of the `targetNamespace` attribute for the `<wsdl:definitions>` element that contains the `<wsdl:service>` element when exported. The default value is null. diff --git a/xml/System.Workflow.Runtime.Configuration/WorkflowRuntimeSection.xml b/xml/System.Workflow.Runtime.Configuration/WorkflowRuntimeSection.xml index 165c9403643..94811c44a5b 100644 --- a/xml/System.Workflow.Runtime.Configuration/WorkflowRuntimeSection.xml +++ b/xml/System.Workflow.Runtime.Configuration/WorkflowRuntimeSection.xml @@ -29,7 +29,7 @@ > [!NOTE] > [!INCLUDE[DeprecatedContent](~/includes/deprecatedcontent-md.md)] - <xref:System.Workflow.Runtime.Configuration.WorkflowRuntimeSection> contains settings specified by a <`section`> of type <xref:System.Workflow.Runtime.Configuration.WorkflowRuntimeSection> in a configuration file. The settings specified in a <xref:System.Workflow.Runtime.Configuration.WorkflowRuntimeSection> are used to initialize the workflow run-time engine. Your application can call the <xref:System.Workflow.Runtime.WorkflowRuntime.%23ctor%28System.String%29?displayProperty=nameWithType> constructor to initialize the workflow run-time engine from the appropriately named section of the configuration file. + <xref:System.Workflow.Runtime.Configuration.WorkflowRuntimeSection> contains settings specified by a `<section>` of type <xref:System.Workflow.Runtime.Configuration.WorkflowRuntimeSection> in a configuration file. The settings specified in a <xref:System.Workflow.Runtime.Configuration.WorkflowRuntimeSection> are used to initialize the workflow run-time engine. Your application can call the <xref:System.Workflow.Runtime.WorkflowRuntime.%23ctor%28System.String%29?displayProperty=nameWithType> constructor to initialize the workflow run-time engine from the appropriately named section of the configuration file. If your application does not use configuration files, but you still want to initialize the workflow run-time engine from a <xref:System.Workflow.Runtime.Configuration.WorkflowRuntimeSection> you can configure a <xref:System.Workflow.Runtime.Configuration.WorkflowRuntimeSection> in your application and call the <xref:System.Workflow.Runtime.WorkflowRuntime.%23ctor%28System.Workflow.Runtime.Configuration.WorkflowRuntimeSection%29?displayProperty=nameWithType> constructor. For example, your application might store configuration parameters in a database or it might operate in a trusted environment where configuration files are not used diff --git a/xml/System.Workflow.Runtime.Configuration/WorkflowRuntimeServiceElement.xml b/xml/System.Workflow.Runtime.Configuration/WorkflowRuntimeServiceElement.xml index da5509b3e3e..f112660aded 100644 --- a/xml/System.Workflow.Runtime.Configuration/WorkflowRuntimeServiceElement.xml +++ b/xml/System.Workflow.Runtime.Configuration/WorkflowRuntimeServiceElement.xml @@ -29,7 +29,7 @@ > [!NOTE] > [!INCLUDE[DeprecatedContent](~/includes/deprecatedcontent-md.md)] - A <xref:System.Workflow.Runtime.Configuration.WorkflowRuntimeServiceElement> specifies a host service that should be initialized and activated by the workflow runtime engine. It corresponds to a host service specified in the <`Services`> element in a configuration file. Because the service specified in a WorkflowRuntimeServiceElement will be initialized by the workflow runtime engine it must have at least one constructor that matches one of the following four signatures (the workflow runtime engine will try to match these signatures in the order shown): + A <xref:System.Workflow.Runtime.Configuration.WorkflowRuntimeServiceElement> specifies a host service that should be initialized and activated by the workflow runtime engine. It corresponds to a host service specified in the `<Services>` element in a configuration file. Because the service specified in a WorkflowRuntimeServiceElement will be initialized by the workflow runtime engine it must have at least one constructor that matches one of the following four signatures (the workflow runtime engine will try to match these signatures in the order shown): Service(WorkflowRuntime runtime, NameValueCollection parameters) @@ -98,7 +98,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - The name-value pair specified by name and value is added to the <xref:System.Workflow.Runtime.Configuration.WorkflowRuntimeServiceElement.Parameters%2A> collection. Any attributes other than `type` that are specified in an <`add`> element to the <`Services`> element in the configuration file are added as a name-value pair to the <xref:System.Workflow.Runtime.Configuration.WorkflowRuntimeServiceElement.Parameters%2A> collection. + The name-value pair specified by name and value is added to the <xref:System.Workflow.Runtime.Configuration.WorkflowRuntimeServiceElement.Parameters%2A> collection. Any attributes other than `type` that are specified in an `<add>` element to the `<Services>` element in the configuration file are added as a name-value pair to the <xref:System.Workflow.Runtime.Configuration.WorkflowRuntimeServiceElement.Parameters%2A> collection. ]]></format> </remarks> diff --git a/xml/System.Workflow.Runtime.Configuration/WorkflowRuntimeServiceElementCollection.xml b/xml/System.Workflow.Runtime.Configuration/WorkflowRuntimeServiceElementCollection.xml index be9f55a9016..38cfe8b4de2 100644 --- a/xml/System.Workflow.Runtime.Configuration/WorkflowRuntimeServiceElementCollection.xml +++ b/xml/System.Workflow.Runtime.Configuration/WorkflowRuntimeServiceElementCollection.xml @@ -29,7 +29,7 @@ > [!NOTE] > [!INCLUDE[DeprecatedContent](~/includes/deprecatedcontent-md.md)] - Represents the services specified by the <`Services`> element in a configuration file. + Represents the services specified by the `<Services>` element in a configuration file. ]]></format> </remarks> diff --git a/xml/System.Xml.Serialization/XmlMemberMapping.xml b/xml/System.Xml.Serialization/XmlMemberMapping.xml index 195f8fb602d..0bdf94b0944 100644 --- a/xml/System.Xml.Serialization/XmlMemberMapping.xml +++ b/xml/System.Xml.Serialization/XmlMemberMapping.xml @@ -93,7 +93,7 @@ <format type="text/markdown"><![CDATA[ ## Remarks - A true value for the <xref:System.Xml.Serialization.XmlMemberMapping.Any%2A> property corresponds to the <`any`> element declaration and the `anyAttribute` attribute declaration in an XML Schema document. + A true value for the <xref:System.Xml.Serialization.XmlMemberMapping.Any%2A> property corresponds to the `<any>` element declaration and the `anyAttribute` attribute declaration in an XML Schema document. ]]></format> </remarks>