Skip to content

Commit 8ef4b8f

Browse files
gewarrengewarren
authored
remove empty intros (dotnet#8743)
1 parent bae2371 commit 8ef4b8f

File tree

4 files changed

+25
-155
lines changed

4 files changed

+25
-155
lines changed

‎xml/System.Activities.DurableInstancing/SqlWorkflowInstanceStore.xml

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -19,14 +19,8 @@
1919
<format type="text/markdown"><![CDATA[
2020
2121
## Remarks
22-
<xref:System.Activities.DurableInstancing.SqlWorkflowInstanceStore> uses the <xref:System.Runtime.Serialization.NetDataContractSerializer> to serialize complex types; all types used in workflows to be persisted with this instance store must be serializable using <xref:System.Runtime.Serialization.NetDataContractSerializer>.
23-
24-
25-
26-
## Examples
27-
The following code sample demonstrates creating a <xref:System.Activities.DurableInstancing.SqlWorkflowInstanceStore>. This example is from the [Persistence Participants](/dotnet/framework/windows-workflow-foundation/persistence-participants) sample.
28-
29-
22+
<xref:System.Activities.DurableInstancing.SqlWorkflowInstanceStore> uses the <xref:System.Runtime.Serialization.NetDataContractSerializer> to serialize complex types; all types used in workflows to be persisted with this instance store must be serializable using <xref:System.Runtime.Serialization.NetDataContractSerializer>.
23+
3024
]]></format>
3125
</remarks>
3226
</Docs>

‎xml/System.Activities.Statements/TryCatch.xml

Lines changed: 3 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -22,10 +22,6 @@
2222
2323
> [!NOTE]
2424
> The <xref:System.Activities.Statements.TryCatch.Finally%2A> activity member of a <xref:System.Activities.Statements.TryCatch> activity that is the child of a <xref:System.Activities.Statements.TransactionScope> will not execute if an unhandled exception propagates past the <xref:System.Activities.Statements.TransactionScope> boundary.
25-
26-
## Examples
27-
28-
The following code sample demonstrates creating a <xref:System.Activities.Statements.TransactionScope> activity.
2925
3026
]]></format>
3127
</remarks>
@@ -45,15 +41,7 @@ The following code sample demonstrates creating a <xref:System.Activities.Statem
4541
<Parameters />
4642
<Docs>
4743
<summary>Creates a new instance of the <see cref="M:System.Activities.Statements.TryCatch.#ctor" /> class.</summary>
48-
<remarks>
49-
<format type="text/markdown"><![CDATA[
50-
51-
## Examples
52-
53-
The following code sample demonstrates creating a <xref:System.Activities.Statements.TransactionScope> activity.
54-
55-
]]></format>
56-
</remarks>
44+
<remarks>To be added.</remarks>
5745
</Docs>
5846
</Member>
5947
<Member MemberName="CacheMetadata">
@@ -133,10 +121,6 @@ The following code sample demonstrates creating a <xref:System.Activities.Statem
133121
134122
## Remarks
135123
Catches are evaluated in the order in which they are added to the collection. If an exact match for the exception type is found, the matching <xref:System.Activities.Statements.Catch> activity is executed. If no exact match is found, the <xref:System.Activities.Statements.Catch> with the closest matching <xref:System.Activities.Statements.Catch.ExceptionType%2A> is executed.
136-
137-
## Examples
138-
139-
The following code sample demonstrates setting the Catches property of a <xref:System.Activities.Statements.TransactionScope> activity.
140124
141125
Once placed in the designer, <xref:System.Activities.Statements.Catch> activities cannot be reordered in the designer. To reorder the collection of <xref:System.Activities.Statements.Catch> activities, either delete and re-add them in the correct order, or use the XAML (code) view for the workflow.
142126
@@ -204,15 +188,7 @@ The following code sample demonstrates setting the Catches property of a <xref:S
204188
<Docs>
205189
<summary>The activity to be executed when the <see cref="P:System.Activities.Statements.TryCatch.Try" /> and any necessary activities in the <see cref="P:System.Activities.Statements.TryCatch.Catches" /> collection complete execution.</summary>
206190
<value>The activity that represents the <see cref="P:System.Activities.Statements.TryCatch.Finally" /> logic.</value>
207-
<remarks>
208-
<format type="text/markdown"><![CDATA[
209-
210-
## Examples
211-
212-
The following code sample demonstrates setting the <xref:System.Activities.Statements.TryCatch.Finally%2A> property of a <xref:System.Activities.Statements.TransactionScope> activity.
213-
214-
]]></format>
215-
</remarks>
191+
<remarks>To be added.</remarks>
216192
</Docs>
217193
</Member>
218194
<Member MemberName="OnCreateDynamicUpdateMap">
@@ -277,15 +253,7 @@ The following code sample demonstrates setting the <xref:System.Activities.State
277253
<Docs>
278254
<summary>The activity first executed when the <see cref="T:System.Activities.Statements.TryCatch" /> executes.</summary>
279255
<value>The activity.</value>
280-
<remarks>
281-
<format type="text/markdown"><![CDATA[
282-
283-
## Examples
284-
285-
The following code sample demonstrates setting the Try property of a <xref:System.Activities.Statements.TransactionScope> activity.
286-
287-
]]></format>
288-
</remarks>
256+
<remarks>To be added.</remarks>
289257
</Docs>
290258
</Member>
291259
<Member MemberName="UpdateInstance">

‎xml/System.Security/NamedPermissionSet.xml

Lines changed: 14 additions & 66 deletions
Original file line numberDiff line numberDiff line change
@@ -49,14 +49,8 @@
4949
5050
[!INCLUDE[cas-deprecated](~/includes/cas-deprecated.md)]
5151
52-
Named permission sets are used in security policy administration to specify the permissions to be granted to code that belongs to certain code groups. Names are strings of alphanumeric characters. Description strings can consist of any printable characters.
53-
54-
55-
56-
## Examples
57-
The following code example shows the use of members of the <xref:System.Security.NamedPermissionSet> class.
58-
59-
52+
Named permission sets are used in security policy administration to specify the permissions to be granted to code that belongs to certain code groups. Names are strings of alphanumeric characters. Description strings can consist of any printable characters.
53+
6054
]]></format>
6155
</remarks>
6256
</Docs>
@@ -220,15 +214,7 @@
220214
<param name="name">The name for the named permission set.</param>
221215
<param name="permSet">The permission set from which to take the value of the new named permission set.</param>
222216
<summary>Initializes a new instance of the <see cref="T:System.Security.NamedPermissionSet" /> class with the specified name from a permission set.</summary>
223-
<remarks>
224-
<format type="text/markdown"><![CDATA[
225-
226-
## Examples
227-
The following code example shows the use of the <xref:System.Security.NamedPermissionSet.%23ctor%2A> constructor to create a new <xref:System.Security.NamedPermissionSet> object. This code example is part of a larger example provided for the <xref:System.Security.NamedPermissionSet> class.
228-
229-
230-
]]></format>
231-
</remarks>
217+
<remarks>To be added.</remarks>
232218
<exception cref="T:System.ArgumentException">The <paramref name="name" /> parameter is <see langword="null" /> or is an empty string ("").</exception>
233219
</Docs>
234220
</Member>
@@ -273,15 +259,7 @@
273259
<Docs>
274260
<summary>Creates a permission set copy from a named permission set.</summary>
275261
<returns>A permission set that is a copy of the permissions in the named permission set.</returns>
276-
<remarks>
277-
<format type="text/markdown"><![CDATA[
278-
279-
## Examples
280-
The following code example shows the use of the <xref:System.Security.NamedPermissionSet.Copy%2A> method to create a copy of the current <xref:System.Security.NamedPermissionSet>. This code example is part of a larger example provided for the <xref:System.Security.NamedPermissionSet> class.
281-
282-
283-
]]></format>
284-
</remarks>
262+
<remarks>To be added.</remarks>
285263
</Docs>
286264
</Member>
287265
<Member MemberName="Copy">
@@ -356,14 +334,8 @@
356334
<format type="text/markdown"><![CDATA[
357335
358336
## Remarks
359-
The description helps the administrator understand in words what permissions the set contains and its intended use.
360-
361-
362-
363-
## Examples
364-
The following code example shows the use of the <xref:System.Security.NamedPermissionSet.Description%2A> property to display the description of the current <xref:System.Security.NamedPermissionSet>. This code example is part of a larger example provided for the <xref:System.Security.NamedPermissionSet> class.
365-
366-
337+
The description helps the administrator understand in words what permissions the set contains and its intended use.
338+
367339
]]></format>
368340
</remarks>
369341
</Docs>
@@ -419,14 +391,8 @@
419391
<format type="text/markdown"><![CDATA[
420392
421393
## Remarks
422-
For more information, see <xref:System.Object.Equals%2A>.
423-
424-
425-
426-
## Examples
427-
The following code example shows the use of the <xref:System.Security.NamedPermissionSet.Equals%2A> method to compare two <xref:System.Security.NamedPermissionSet> objects. This code example is part of a larger example provided for the <xref:System.Security.NamedPermissionSet> class.
428-
429-
394+
For more information, see <xref:System.Object.Equals%2A>.
395+
430396
]]></format>
431397
</remarks>
432398
</Docs>
@@ -468,14 +434,8 @@
468434
<format type="text/markdown"><![CDATA[
469435
470436
## Remarks
471-
This method recreates the state of a named permission set from an XML element previously created by <xref:System.Security.NamedPermissionSet.ToXml%2A>.
472-
473-
474-
475-
## Examples
476-
The following code example shows the use of the <xref:System.Security.NamedPermissionSet.FromXml%2A> method to recreate a <xref:System.Security.NamedPermissionSet> object. This code example is part of a larger example provided for the <xref:System.Security.NamedPermissionSet> class.
477-
478-
437+
This method recreates the state of a named permission set from an XML element previously created by <xref:System.Security.NamedPermissionSet.ToXml%2A>.
438+
479439
]]></format>
480440
</remarks>
481441
<exception cref="T:System.ArgumentException">The <paramref name="et" /> parameter is not a valid representation of a named permission set.</exception>
@@ -562,14 +522,8 @@
562522
<format type="text/markdown"><![CDATA[
563523
564524
## Remarks
565-
Code groups refer to permission sets by name.
566-
567-
568-
569-
## Examples
570-
The following code example shows the use of the <xref:System.Security.NamedPermissionSet.Name%2A> property to display the name of a <xref:System.Security.NamedPermissionSet>. This code example is part of a larger example provided for the <xref:System.Security.NamedPermissionSet> class.
571-
572-
525+
Code groups refer to permission sets by name.
526+
573527
]]></format>
574528
</remarks>
575529
<exception cref="T:System.ArgumentException">The name is <see langword="null" /> or is an empty string ("").</exception>
@@ -616,14 +570,8 @@
616570
<format type="text/markdown"><![CDATA[
617571
618572
## Remarks
619-
Use <xref:System.Security.NamedPermissionSet.FromXml%2A> to recreate the state represented by the returned element.
620-
621-
622-
623-
## Examples
624-
The following code example shows the use of the <xref:System.Security.NamedPermissionSet.ToXml%2A> method to recreate a <xref:System.Security.NamedPermissionSet> object. This code example is part of a larger example provided for the <xref:System.Security.NamedPermissionSet> class.
625-
626-
573+
Use <xref:System.Security.NamedPermissionSet.FromXml%2A> to recreate the state represented by the returned element.
574+
627575
]]></format>
628576
</remarks>
629577
</Docs>

‎xml/System.ServiceModel.Channels/ISecurityCapabilities.xml

Lines changed: 6 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@
3333
<format type="text/markdown"><![CDATA[
3434
3535
## Examples
36-
For a full implementation see the [NetHttpBinding](https://msdn.microsoft.com/library/1f2bb9b2-e0c5-4e8e-a9d3-703575bb159c) sample
36+
For a full implementation, see the [NetHttpBinding](/previous-versions/dotnet/netframework-4.0/aa395198(v=vs.100)) sample.
3737
3838
]]></format>
3939
</remarks>
@@ -67,15 +67,7 @@
6767
<Docs>
6868
<summary>Gets the protection level requests supported by the binding.</summary>
6969
<value>The <see cref="T:System.Net.Security.ProtectionLevel" /> that specifies the protection level requests supported by the binding.</value>
70-
<remarks>
71-
<format type="text/markdown"><![CDATA[
72-
73-
## Examples
74-
The following code snippet illustrates how to implement this property:
75-
76-
77-
]]></format>
78-
</remarks>
70+
<remarks>To be added.</remarks>
7971
</Docs>
8072
</Member>
8173
<Member MemberName="SupportedResponseProtectionLevel">
@@ -106,15 +98,7 @@
10698
<Docs>
10799
<summary>Gets the protection level responses supported by the binding.</summary>
108100
<value>The <see cref="T:System.Net.Security.ProtectionLevel" /> that specifies the protection level responses supported by the binding.</value>
109-
<remarks>
110-
<format type="text/markdown"><![CDATA[
111-
112-
## Examples
113-
The following code snippet illustrates how to implement this property:
114-
115-
116-
]]></format>
117-
</remarks>
101+
<remarks>To be added.</remarks>
118102
</Docs>
119103
</Member>
120104
<Member MemberName="SupportsClientAuthentication">
@@ -146,15 +130,7 @@
146130
<summary>Gets a value that indicates whether the binding supports client authentication.</summary>
147131
<value>
148132
<see langword="true" /> if the binding can support client authentication; otherwise, <see langword="false" />.</value>
149-
<remarks>
150-
<format type="text/markdown"><![CDATA[
151-
152-
## Examples
153-
The following code snippet illustrates how to implement this property:
154-
155-
156-
]]></format>
157-
</remarks>
133+
<remarks>To be added.</remarks>
158134
</Docs>
159135
</Member>
160136
<Member MemberName="SupportsClientWindowsIdentity">
@@ -186,15 +162,7 @@
186162
<summary>Gets a value that indicates whether the binding supports client Windows identity.</summary>
187163
<value>
188164
<see langword="true" /> if the binding can support client Windows identity; otherwise, <see langword="false" />.</value>
189-
<remarks>
190-
<format type="text/markdown"><![CDATA[
191-
192-
## Examples
193-
The following code snippet illustrates how to implement this property:
194-
195-
196-
]]></format>
197-
</remarks>
165+
<remarks>To be added.</remarks>
198166
</Docs>
199167
</Member>
200168
<Member MemberName="SupportsServerAuthentication">
@@ -226,15 +194,7 @@
226194
<summary>Gets a value that indicates whether the binding supports server authentication.</summary>
227195
<value>
228196
<see langword="true" /> if the binding can support server authentication; otherwise, <see langword="false" />.</value>
229-
<remarks>
230-
<format type="text/markdown"><![CDATA[
231-
232-
## Examples
233-
The following code snippet illustrates how to implement this property:
234-
235-
236-
]]></format>
237-
</remarks>
197+
<remarks>To be added.</remarks>
238198
</Docs>
239199
</Member>
240200
</Members>

0 commit comments

Comments
 (0)