Skip to content

Commit 13c414e

Browse files
Ron PetrushaBillWagner
authored andcommitted
Restored enumeration member remarks, Part 9 (#2646)
* Restored enumeration member remarks, Part 9 * Corrected misformred xml
1 parent 679a10c commit 13c414e

File tree

11 files changed

+68
-343
lines changed

11 files changed

+68
-343
lines changed

xml/System.Transactions/IsolationLevel.xml

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@
3434
3535
The lowest isolation level, `ReadUncommitted`, allows many transactions to operate on a data store simultaneously and provides no protection against data corruption due to interruptive transactions. The highest isolation level, `Serializable`, provides a high degree of protection against interruptive transactions, but requires that each transaction complete before any other transactions are allowed to operate on the data.
3636
37-
The isolation level of a transaction is determined when the transaction is created. By default, the <xref:System.Transactions> infrastructure creates `Serializable` transactions. You can determine the isolation level of an existing transaction using the <xref:System.Transactions.Transaction.IsolationLevel%2A> property of a transaction.
37+
The isolation level of a transaction is determined when the transaction is created. By default, the <xref:System.Transactions> infrastructure creates `Serializable` transactions. You can determine the isolation level of an existing transaction by using the <xref:System.Transactions.Transaction.IsolationLevel%2A?displayProperty=nameWithType> property of a transaction.
3838
3939
]]></format>
4040
</remarks>
@@ -229,15 +229,7 @@
229229
</ReturnValue>
230230
<MemberValue>4</MemberValue>
231231
<Docs>
232-
<summary>Volatile data can be read. Before a transaction modifies data, it verifies if another transaction has changed the data after it was initially read. If the data has been updated, an error is raised. This allows a transaction to get to the previously committed value of the data.</summary>
233-
<remarks>
234-
<format type="text/markdown"><![CDATA[
235-
236-
## Remarks
237-
When you try to promote a transaction that was created with this isolation level, an <xref:System.InvalidOperationException> is thrown with the error message "Transactions with IsolationLevel Snapshot cannot be promoted".
238-
239-
]]></format>
240-
</remarks>
232+
<summary><para>Volatile data can be read. Before a transaction modifies data, it verifies if another transaction has changed the data after it was initially read. If the data has been updated, an error is raised. This allows a transaction to get to the previously committed value of the data.</para><para>When you try to promote a transaction that was created with the <see langword="Snapshot" /> isolation level, an <see cref="T:System.InvalidOperationException" /> is thrown with the error message "Transactions with IsolationLevel Snapshot cannot be promoted".</para></summary>
241233
</Docs>
242234
</Member>
243235
<Member MemberName="Unspecified">

xml/System.Transactions/TransactionScopeAsyncFlowOption.xml

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -94,15 +94,7 @@
9494
</ReturnValue>
9595
<MemberValue>0</MemberValue>
9696
<Docs>
97-
<summary>Specifies that transaction flow across thread continuations is suppressed.</summary>
98-
<remarks>
99-
<format type="text/markdown"><![CDATA[
100-
101-
## Remarks
102-
This is the default setting if no <xref:System.Transactions.TransactionScopeAsyncFlowOption> is specified in the <xref:System.Transactions.TransactionScope.%23ctor%2A> constructor.
103-
104-
]]></format>
105-
</remarks>
97+
<summary>Specifies that transaction flow across thread continuations is suppressed. This is the default setting if no <see langword="TransactionScopeAsyncFlowOption" /> is specified in the <see cref="Overload:System.Transactions.TransactionScope.#ctor" /> constructor.</summary>
10698
</Docs>
10799
</Member>
108100
</Members>

xml/System.Web.Configuration/MachineKeyValidation.xml

Lines changed: 9 additions & 77 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,7 @@
2121
## Remarks
2222
ASP.NET uses a hash-based message authentication code (HMAC) to help detect whether data that is used for forms authentication or view state has been tampered with. The HMAC is generated when view state content is created, and the HMAC is checked on subsequent requests. The HMAC helps ASP.NET determine whether someone has changed data that is sent between the server and the client, but the data can be read by anyone as it travels through the Internet unless it is also encrypted. By default, view state is validated but not encrypted. For more information, see <xref:System.Web.UI.Page.ViewStateEncryptionMode%2A> and <xref:System.Web.UI.Page.RegisterRequiresViewStateEncryption%2A>.
2323
24-
The <xref:System.Web.Configuration.MachineKeyValidation> enumeration lets you specify the algorithm that ASP.NET uses to create the HMAC. The default value is HMACSHA256. ASP.NET uses the value of the <xref:System.Web.Configuration.MachineKeySection.ValidationKey%2A> property with the selected algorithm to generate the HMAC.
25-
26-
24+
The `MachineKeyValidation` enumeration lets you specify the algorithm that ASP.NET uses to create the HMAC. The default value is `HMACSHA256`. ASP.NET uses the value of the <xref:System.Web.Configuration.MachineKeySection.ValidationKey%2A> property with the selected algorithm to generate the HMAC.
2725
2826
## Examples
2927
The following code example shows how to use the <xref:System.Web.Configuration.MachineKeyValidation> enumeration. In the example, `configSection` is an instance of <xref:System.Web.Configuration.MachineKeySection>.This code example is part of a larger example provided for the <xref:System.Web.Configuration.MachineKeySection> class.
@@ -59,15 +57,7 @@
5957
</ReturnValue>
6058
<MemberValue>3</MemberValue>
6159
<Docs>
62-
<summary>Specifies that ASP.NET uses the <see langword="AES" /> (Rijndael) encryption algorithm.</summary>
63-
<remarks>
64-
<format type="text/markdown"><![CDATA[
65-
66-
## Remarks
67-
Choose this option if you want to encrypt view state in your Web application. If you choose this option, the <xref:System.Web.Configuration.MachineKeySection.DecryptionKey%2A> property will be used for encryption and decryption, and the `HMACSHA1` hash algorithm will be used with the <xref:System.Web.Configuration.MachineKeySection.ValidationKey%2A> property for validation.
68-
69-
]]></format>
70-
</remarks>
60+
<summary><para>Specifies that ASP.NET uses the <see langword="AES" /> (Rijndael) encryption algorithm. Choose this option if you want to encrypt view state in your Web application.</para><para>If you choose this option, the <see cref="P:System.Web.Configuration.MachineKeySection.DecryptionKey" /> property will be used for encryption and decryption, and the <see langword="HMACSHA1" /> hash algorithm will be used with the <see cref="P:System.Web.Configuration.MachineKeySection.ValidationKey" /> property for validation.</para></summary>
7161
<altmember cref="T:System.Web.Configuration.MachineKeyValidation" />
7262
</Docs>
7363
</Member>
@@ -88,17 +78,7 @@
8878
</ReturnValue>
8979
<MemberValue>7</MemberValue>
9080
<Docs>
91-
<summary>Specifies that ASP.NET uses a custom hashing algorithm.</summary>
92-
<remarks>
93-
<format type="text/markdown"><![CDATA[
94-
95-
## Remarks
96-
The custom hashing algorithm can be implemented in any class that derives from <xref:System.Security.Cryptography.KeyedHashAlgorithm>.
97-
98-
The custom algorithm is typically specified declaratively in the validation attribute of the element, in the format `alg:`*algorithm_name*. For information about how to specify a custom algorithm in code, see the <xref:System.Web.Configuration.MachineKeySection.ValidationAlgorithm%2A?displayProperty=nameWithType> property.
99-
100-
]]></format>
101-
</remarks>
81+
<summary><para>Specifies that ASP.NET uses a custom hashing algorithm. The custom hashing algorithm can be implemented in any class that derives from <see cref="T:System.Security.Cryptography.KeyedHashAlgorithm" />.</para><para>The custom algorithm is typically specified declaratively in the <c>validation</c> attribute of the <see href="https://docs.microsoft.com/en-us/previous-versions/dotnet/netframework-4.0/w8h3skw9(v=vs.100)">machineKey</see> element, in the format <c>alg:`*algorithm_name*</c>. For information about how to specify a custom algorithm in code, see the <see cref="P:System.Web.Configuration.MachineKeySection.ValidationAlgorithm" /> property.</para></summary>
10282
<altmember cref="T:System.Web.Configuration.MachineKeyValidation" />
10383
</Docs>
10484
</Member>
@@ -119,15 +99,7 @@
11999
</ReturnValue>
120100
<MemberValue>4</MemberValue>
121101
<Docs>
122-
<summary>Specifies that ASP.NET uses the <see langword="HMACSHA256" /> hashing algorithm. This is the default value.</summary>
123-
<remarks>
124-
<format type="text/markdown"><![CDATA[
125-
126-
## Remarks
127-
`HMACSHA256` is an SHA2 hashing algorithm that generates a 256-bit hash code.
128-
129-
]]></format>
130-
</remarks>
102+
<summary>Specifies that ASP.NET uses the <see langword="HMACSHA256" /> hashing algorithm, which is an SHA2 hashing algorithm that generates a 256-bit hash code. This is the default value.</summary>
131103
<altmember cref="T:System.Web.Configuration.MachineKeyValidation" />
132104
</Docs>
133105
</Member>
@@ -148,15 +120,7 @@
148120
</ReturnValue>
149121
<MemberValue>5</MemberValue>
150122
<Docs>
151-
<summary>Specifies that ASP.NET uses the <see langword="HMACSHA384" /> hashing algorithm.</summary>
152-
<remarks>
153-
<format type="text/markdown"><![CDATA[
154-
155-
## Remarks
156-
`HMACSHA384` is an SHA2 hashing algorithm that generates a 384-bit hash code. This option is available for applications that require stronger security than is provided by the `HMACSHA256` algorithm.
157-
158-
]]></format>
159-
</remarks>
123+
<summary>Specifies that ASP.NET uses the <see langword="HMACSHA384" /> hashing algorithm, which is an SHA2 hashing algorithm that generates a 384-bit hash code. This option is available for applications that require stronger security than provided by the <see langword="HMACSHA256" /> algorithm..</summary>
160124
<altmember cref="T:System.Web.Configuration.MachineKeyValidation" />
161125
</Docs>
162126
</Member>
@@ -177,15 +141,7 @@
177141
</ReturnValue>
178142
<MemberValue>6</MemberValue>
179143
<Docs>
180-
<summary>Specifies that ASP.NET uses the <see langword="HMACSHA512" /> hashing algorithm.</summary>
181-
<remarks>
182-
<format type="text/markdown"><![CDATA[
183-
184-
## Remarks
185-
`HMACSHA512` is an SHA2 hashing algorithm that generates a 512-bit hash code. This option is available for applications that require stronger security than is provided by the `HMACSHA384` algorithm.
186-
187-
]]></format>
188-
</remarks>
144+
<summary>Specifies that ASP.NET uses the <see langword="HMACSHA512" /> hashing algorithm, which is an SHA2 hashing algorithm that generates a 512-bit hash code. This option is available for applications that require stronger security than provided by the <see langword=">HMACSHA384" /> algorithm.</summary>
189145
<altmember cref="T:System.Web.Configuration.MachineKeyValidation" />
190146
</Docs>
191147
</Member>
@@ -207,15 +163,7 @@
207163
</ReturnValue>
208164
<MemberValue>0</MemberValue>
209165
<Docs>
210-
<summary>Specifies that ASP.NET uses the Message Digest 5 (<see langword="MD5" />) hashing algorithm.</summary>
211-
<remarks>
212-
<format type="text/markdown"><![CDATA[
213-
214-
## Remarks
215-
`MD5` is a hashing algorithm that generates a 128-bit hash value. This option is included for legacy purposes and should be selected only if compatibility with earlier versions of ASP.NET is required.
216-
217-
]]></format>
218-
</remarks>
166+
<summary>Specifies that ASP.NET uses the Message Digest 5 (<see langword="MD5" />) hashing algorithm, which is a hashing algorithm that generates a 128-bit hash value. This is a legacy value that should be selected only if compatibility with earlier versions of ASP.NET is required.</summary>
219167
<altmember cref="T:System.Web.Configuration.MachineKeyValidation" />
220168
</Docs>
221169
</Member>
@@ -237,15 +185,7 @@
237185
</ReturnValue>
238186
<MemberValue>1</MemberValue>
239187
<Docs>
240-
<summary>Specifies that ASP.NET uses the <see langword="HMACSHA1" /> hash algorithm.</summary>
241-
<remarks>
242-
<format type="text/markdown"><![CDATA[
243-
244-
## Remarks
245-
`HMACSHA1` is a hashing algorithm that generates a 160-bit hash value. This option is included for legacy purposes and should be selected only if compatibility with earlier versions of ASP.NET is required.
246-
247-
]]></format>
248-
</remarks>
188+
<summary>Specifies that ASP.NET uses the <see langword="HMACSHA1" /> hash algorithm, which is a hashing algorithm that generates a 160-bit hash value. This is a legacy value that should be selected only if compatibility with earlier versions of ASP.NET is required.</summary>
249189
<altmember cref="T:System.Web.Configuration.MachineKeyValidation" />
250190
</Docs>
251191
</Member>
@@ -267,15 +207,7 @@
267207
</ReturnValue>
268208
<MemberValue>2</MemberValue>
269209
<Docs>
270-
<summary>Specifies that ASP.NET uses the TripleDES (<see langword="3DES" />) encryption algorithm.</summary>
271-
<remarks>
272-
<format type="text/markdown"><![CDATA[
273-
274-
## Remarks
275-
TripleDES is an encryption algorithm that is used only if you specify that view state is encrypted. This option is included for legacy purposes and should be selected only if compatibility with earlier versions of ASP.NET is required.
276-
277-
]]></format>
278-
</remarks>
210+
<summary>Specifies that ASP.NET uses the TripleDES (<see langword="3DES" />) encryption algorithm, which is an encryption algorithm that is used only if you specify that view state is encrypted. This is a legacy value that should be selected only if compatibility with earlier versions of ASP.NET is required..</summary>
279211
<altmember cref="T:System.Web.Configuration.MachineKeyValidation" />
280212
</Docs>
281213
</Member>

xml/System.Web.Configuration/ProcessModelComAuthenticationLevel.xml

Lines changed: 9 additions & 58 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,10 @@
1919
<format type="text/markdown"><![CDATA[
2020
2121
## Remarks
22-
The <xref:System.Web.Configuration.ProcessModelComAuthenticationLevel> enumerates the values to use when you set the <xref:System.Web.Configuration.ProcessModelSection.ComAuthenticationLevel%2A> property.
22+
23+
`ProcessModelComAuthenticationLevel` defines the values to use when you set the <xref:System.Web.Configuration.ProcessModelSection.ComAuthenticationLevel%2A?displayProperty=nameWithType> property.
2324
24-
The default is Connect.
25+
The default is `Connect`.
2526
2627
> [!NOTE]
2728
> The <xref:System.Web.Configuration.ProcessModelComAuthenticationLevel.Connect> settings are relevant only when you use the ASP.NET process model (Internet Information Services [IIS] 5.n or compatible mode on IIS 6 only).
@@ -57,15 +58,7 @@
5758
</ReturnValue>
5859
<MemberValue>1</MemberValue>
5960
<Docs>
60-
<summary>Specifies that DCOM authenticates the credentials of the client. This field is constant.</summary>
61-
<remarks>
62-
<format type="text/markdown"><![CDATA[
63-
64-
## Remarks
65-
DCOM authenticates the credentials of the client when the server receives the request at the beginning of each remote procedure call.
66-
67-
]]></format>
68-
</remarks>
61+
<summary>Specifies that DCOM authenticates the credentials of the client when the server receives the request at the beginning of each remote procedure call.</summary>
6962
</Docs>
7063
</Member>
7164
<Member MemberName="Connect">
@@ -86,17 +79,7 @@
8679
</ReturnValue>
8780
<MemberValue>2</MemberValue>
8881
<Docs>
89-
<summary>Specifies that DCOM authenticates the credentials of the client. This field is constant.</summary>
90-
<remarks>
91-
<format type="text/markdown"><![CDATA[
92-
93-
## Remarks
94-
DCOM authenticates the credentials of the client only when the client establishes a relationship with the server.
95-
96-
This is the default value.
97-
98-
]]></format>
99-
</remarks>
82+
<summary>Specifies that DCOM authenticates the credentials of the client only when the client establishes a relationship with the server. This is the default value. </summary>
10083
</Docs>
10184
</Member>
10285
<Member MemberName="Default">
@@ -117,15 +100,7 @@
117100
</ReturnValue>
118101
<MemberValue>3</MemberValue>
119102
<Docs>
120-
<summary>Specifies that DCOM determines the authentication level. This field is constant.</summary>
121-
<remarks>
122-
<format type="text/markdown"><![CDATA[
123-
124-
## Remarks
125-
DCOM determines the authentication level using its normal security-negotiation algorithm.
126-
127-
]]></format>
128-
</remarks>
103+
<summary>Specifies that DCOM determines the authentication level using its normal security-negotiation algorithm.</summary>
129104
</Docs>
130105
</Member>
131106
<Member MemberName="None">
@@ -167,15 +142,7 @@
167142
</ReturnValue>
168143
<MemberValue>4</MemberValue>
169144
<Docs>
170-
<summary>Specifies that DCOM verifies that all data received is from the expected client. This field is constant.</summary>
171-
<remarks>
172-
<format type="text/markdown"><![CDATA[
173-
174-
## Remarks
175-
The datagram transports always use Pkt authentication.
176-
177-
]]></format>
178-
</remarks>
145+
<summary>Specifies that DCOM verifies that all data received is from the expected client. The datagram transports always use Pkt authentication.</summary>
179146
</Docs>
180147
</Member>
181148
<Member MemberName="PktIntegrity">
@@ -196,15 +163,7 @@
196163
</ReturnValue>
197164
<MemberValue>5</MemberValue>
198165
<Docs>
199-
<summary>Specifies that DCOM authenticates and verifies the data transferred. This field is constant.</summary>
200-
<remarks>
201-
<format type="text/markdown"><![CDATA[
202-
203-
## Remarks
204-
DCOM verifies that none of the data transferred between the client and the server has been modified.
205-
206-
]]></format>
207-
</remarks>
166+
<summary>Specifies that DCOM authenticates and verifies that none of the data transferred between the client and the server has been modified.</summary>
208167
</Docs>
209168
</Member>
210169
<Member MemberName="PktPrivacy">
@@ -225,15 +184,7 @@
225184
</ReturnValue>
226185
<MemberValue>6</MemberValue>
227186
<Docs>
228-
<summary>Specifies that DCOM authenticates all previous levels and does encryption. This field is constant.</summary>
229-
<remarks>
230-
<format type="text/markdown"><![CDATA[
231-
232-
## Remarks
233-
DCOM authenticates all previous levels and encrypts the argument value of each remote procedure call.
234-
235-
]]></format>
236-
</remarks>
187+
<summary>Specifies that DCOM authenticates all previous levels and encrypts the argument value of each remote procedure call.</summary>
237188
</Docs>
238189
</Member>
239190
</Members>

0 commit comments

Comments
 (0)