Skip to content

Commit 8862380

Browse files
authored
Remove /previous-versions links from docs (#12535)
1 parent 0c25088 commit 8862380

File tree

612 files changed

+1232
-3322
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

612 files changed

+1232
-3322
lines changed

xml/Microsoft.Win32/FileDialog.xml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -948,8 +948,6 @@ Open and save file dialog boxes have a **Favorite Links** panel on the left side
948948
949949
If more than one file name is selected (length of <xref:Microsoft.Win32.FileDialog.SafeFileNames*> is greater than one) then this property contains only the first selected file name.
950950
951-
See [Safe File Upload from an XBAP Sample](/previous-versions/dotnet/netframework-3.5/aa358504(v=vs.90)).
952-
953951
]]></format>
954952
</remarks>
955953
</Docs>

xml/System.Activities.Statements/CompensableActivity.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@
2828
<format type="text/markdown"><![CDATA[
2929
3030
## Remarks
31-
<xref:System.Activities.Statements.CompensableActivity> allows a developer to specify a <xref:System.Activities.Statements.CompensableActivity.Body*> activity that defines a long-running task that performs their core business logic. It also allows the developer to optionally specify a compensation and confirmation activity to schedule appropriate business logic in the event of errors or successful completion of the <xref:System.Activities.Statements.CompensableActivity.Body*>. Compensation and confirmation of a <xref:System.Activities.Statements.CompensableActivity> is invoked by using the <xref:System.Activities.Statements.CompensationToken> returned by the <xref:System.Activities.Statements.CompensableActivity>. <xref:System.Activities.Statements.CompensationToken> is an opaque, typed object returned after successful completion of a <xref:System.Activities.Statements.CompensableActivity> activity's <xref:System.Activities.Statements.CompensableActivity.Body*>. This <xref:System.Activities.Statements.CompensationToken> is used by the <xref:System.Activities.Statements.Confirm> and <xref:System.Activities.Statements.Compensate> activities to explicitly invoke confirmation and compensation of a <xref:System.Activities.Statements.CompensableActivity>. <xref:System.Activities.Statements.CompensableActivity> can be composed in a nested hierarchical fashion in the workflow. For more information, see [Compensation Programming Model](/previous-versions/dd489415(v=vs.100)).
31+
<xref:System.Activities.Statements.CompensableActivity> allows a developer to specify a <xref:System.Activities.Statements.CompensableActivity.Body*> activity that defines a long-running task that performs their core business logic. It also allows the developer to optionally specify a compensation and confirmation activity to schedule appropriate business logic in the event of errors or successful completion of the <xref:System.Activities.Statements.CompensableActivity.Body*>. Compensation and confirmation of a <xref:System.Activities.Statements.CompensableActivity> is invoked by using the <xref:System.Activities.Statements.CompensationToken> returned by the <xref:System.Activities.Statements.CompensableActivity>. <xref:System.Activities.Statements.CompensationToken> is an opaque, typed object returned after successful completion of a <xref:System.Activities.Statements.CompensableActivity> activity's <xref:System.Activities.Statements.CompensableActivity.Body*>. This <xref:System.Activities.Statements.CompensationToken> is used by the <xref:System.Activities.Statements.Confirm> and <xref:System.Activities.Statements.Compensate> activities to explicitly invoke confirmation and compensation of a <xref:System.Activities.Statements.CompensableActivity>. <xref:System.Activities.Statements.CompensableActivity> can be composed in a nested hierarchical fashion in the workflow.
3232
3333
]]></format>
3434
</remarks>

xml/System.Activities.Statements/CompensationToken.xml

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -21,14 +21,7 @@
2121
</Attributes>
2222
<Docs>
2323
<summary>Provides a means to explicitly confirm or compensate a <see cref="T:System.Activities.Statements.CompensableActivity" /> once the <see cref="P:System.Activities.Statements.CompensableActivity.Body" /> of the <see cref="T:System.Activities.Statements.CompensableActivity" /> has successfully completed.</summary>
24-
<remarks>
25-
<format type="text/markdown"><![CDATA[
26-
27-
## Remarks
28-
For more information, see [Compensation Programming Model](/previous-versions/dd489415(v=vs.100)).
29-
30-
]]></format>
31-
</remarks>
24+
<remarks>To be added.</remarks>
3225
</Docs>
3326
<Members />
3427
</Type>

xml/System.AddIn.Contract/IListContract`1.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@
2525
<format type="text/markdown"><![CDATA[
2626
2727
## Remarks
28-
The <xref:System.AddIn.Pipeline.CollectionAdapters> class uses an <xref:System.AddIn.Contract.IListContract`1> interface to pass collections, in both directions, between the host and the add-in. It is recommended that you use the <xref:System.AddIn.Pipeline.CollectionAdapters> class instead of using this class directly in your code. For an example, see [Walkthrough: Passing Collections Between Hosts and Add-Ins](/previous-versions/dotnet/netframework-4.0/bb384207(v=vs.100)).
28+
The <xref:System.AddIn.Pipeline.CollectionAdapters> class uses an <xref:System.AddIn.Contract.IListContract`1> interface to pass collections, in both directions, between the host and the add-in. It is recommended that you use the <xref:System.AddIn.Pipeline.CollectionAdapters> class instead of using this class directly in your code.
2929
3030
This class can be used to pass objects by reference between application domains because the objects are not serialized.
3131

xml/System.AddIn.Hosting/AddInEnvironment.xml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,6 @@
3838
3939
]]></format>
4040
</remarks>
41-
<related type="Article" href="/previous-versions/dotnet/netframework-4.0/bb384200(v=vs.100)">Add-Ins and Extensibility</related>
4241
</Docs>
4342
<Members>
4443
<Member MemberName=".ctor">

xml/System.AddIn.Hosting/AddInProcess.xml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,6 @@
3434
3535
]]></format>
3636
</remarks>
37-
<related type="Article" href="/previous-versions/dotnet/netframework-4.0/bb384200(v=vs.100)">Add-Ins and Extensibility</related>
3837
</Docs>
3938
<Members>
4039
<MemberGroup MemberName=".ctor">

xml/System.AddIn.Hosting/AddInSecurityLevel.xml

Lines changed: 19 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -22,24 +22,23 @@
2222
<Docs>
2323
<summary>Specifies the trust level that is granted to the application domain that an add-in is loaded into.</summary>
2424
<remarks>
25-
<format type="text/markdown"><![CDATA[
26-
27-
## Remarks
28-
The add-in system activates the add-in with the permission set that corresponds to the trust level specified for the add-in's application domain. That permission set is defined by the common language runtime's code access security (CAS) configuration.
29-
30-
The values of this enumeration cannot be combined by using the bitwise OR operation.
31-
32-
33-
34-
## Examples
35-
The following example activates an add-in with a specified trust level.
36-
25+
<format type="text/markdown"><![CDATA[
26+
27+
## Remarks
28+
The add-in system activates the add-in with the permission set that corresponds to the trust level specified for the add-in's application domain. That permission set is defined by the common language runtime's code access security (CAS) configuration.
29+
30+
The values of this enumeration cannot be combined by using the bitwise OR operation.
31+
32+
33+
34+
## Examples
35+
The following example activates an add-in with a specified trust level.
36+
3737
:::code language="csharp" source="~/snippets/csharp/System.AddIn.Hosting/AddInController/Overview/P3Host.cs" id="Snippet5":::
38-
:::code language="vb" source="~/snippets/visualbasic/System.AddIn.Hosting/AddInController/Overview/p3host.vb" id="Snippet5":::
39-
38+
:::code language="vb" source="~/snippets/visualbasic/System.AddIn.Hosting/AddInController/Overview/p3host.vb" id="Snippet5":::
39+
4040
]]></format>
4141
</remarks>
42-
<related type="Article" href="/previous-versions/dotnet/netframework-4.0/bb384200(v=vs.100)">Add-Ins and Extensibility</related>
4342
</Docs>
4443
<Members>
4544
<Member MemberName="FullTrust">
@@ -86,11 +85,11 @@
8685
<para>- It represents the maximum permission set a host can grant to its add-ins.<para></para>- It allows a ClickOnce or an Extensible Application Markup Language (XAML) Browser Application (XBAP) host to propagate its site of origin to its add-ins, which enables them to contact the server.</para>
8786
</summary>
8887
<remarks>
89-
<format type="text/markdown"><![CDATA[
90-
91-
## Remarks
92-
93-
88+
<format type="text/markdown"><![CDATA[
89+
90+
## Remarks
91+
92+
9493
]]></format>
9594
</remarks>
9695
</Docs>

xml/System.AddIn.Hosting/AddInSegmentDirectoryNotFoundException.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@
2626
<format type="text/markdown"><![CDATA[
2727
2828
## Remarks
29-
When an add-in is activated, its pipeline to the host is constructed. The add-in system requires that pipeline segments be placed in a specified directory structure with specified directory names, as described in [Pipeline Development Requirements](/previous-versions/dotnet/netframework-4.0/bb384240(v=vs.100)).
29+
When an add-in is activated, its pipeline to the host is constructed. The add-in system requires that pipeline segments be placed in a specified directory structure with specified directory names.
3030
3131
]]></format>
3232
</remarks>

xml/System.AddIn.Hosting/AddInStore.xml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,6 @@
4444
4545
]]></format>
4646
</remarks>
47-
<related type="Article" href="/previous-versions/dotnet/netframework-4.0/bb384200(v=vs.100)">Add-Ins and Extensibility</related>
4847
</Docs>
4948
<Members>
5049
<Member MemberName="FindAddIn">

xml/System.AddIn.Hosting/AddInToken.xml

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,6 @@
6464
6565
]]></format>
6666
</remarks>
67-
<related type="Article" href="/previous-versions/dotnet/netframework-4.0/bb384200(v=vs.100)">Add-Ins and Extensibility</related>
6867
</Docs>
6968
<Members>
7069
<MemberGroup MemberName="Activate&lt;T&gt;">
@@ -119,7 +118,6 @@
119118
120119
]]></format>
121120
</remarks>
122-
<related type="Article" href="/previous-versions/dotnet/netframework-4.0/bb384200(v=vs.100)">Add-Ins and Extensibility</related>
123121
</Docs>
124122
</Member>
125123
<Member MemberName="Activate&lt;T&gt;">
@@ -167,7 +165,6 @@
167165
168166
]]></format>
169167
</remarks>
170-
<related type="Article" href="/previous-versions/dotnet/netframework-4.0/bb384200(v=vs.100)">Add-Ins and Extensibility</related>
171168
</Docs>
172169
</Member>
173170
<Member MemberName="Activate&lt;T&gt;">

0 commit comments

Comments
 (0)