Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 80358d2

Browse files
gewarrengewarren
authored
add language slugs (#11220)
1 parent 626a49c commit 80358d2

23 files changed

+53
-69
lines changed

‎xml/Microsoft.VisualBasic.Compatibility.VB6/DirListBox.xml

+1-1
Original file line numberDiff line numberDiff line change
@@ -933,7 +933,7 @@
933933
934934
The `Path` property can also be set to a qualified network path without a drive connection using the following syntax:
935935
936-
```
936+
```txt
937937
\\servername\sharename\path
938938
```
939939

‎xml/Microsoft.VisualBasic.Compatibility.VB6/FileListBox.xml

+1-1
Original file line numberDiff line numberDiff line change
@@ -696,7 +696,7 @@
696696
697697
The `Path` property can also be set to a qualified network path without a drive connection using the following syntax:
698698
699-
```
699+
```txt
700700
\\servername\sharename\path
701701
```
702702

‎xml/Microsoft.Windows.Themes/BulletChrome.xml

+3-2
Original file line numberDiff line numberDiff line change
@@ -66,13 +66,14 @@
6666
<a name="xamlObjectElementUsage_BulletChrome"></a>
6767
## XAML Object Element Usage
6868
69-
```
69+
```xaml
7070
<theme:BulletChrome .../>
7171
```
7272
7373
<a name="xamlValues_BulletChrome"></a>
7474
## XAML Values
75-
`theme:`
75+
76+
`theme:`\
7677
An xmlns prefix for the <xref:Microsoft.Windows.Themes> CLR namespace. Typically, xmlns prefixes and mappings are defined in a XAML root element (not shown).
7778
7879
]]></format>

‎xml/Microsoft.Windows.Themes/ButtonChrome.xml

+2-2
Original file line numberDiff line numberDiff line change
@@ -66,13 +66,13 @@
6666
<a name="xamlObjectElementUsage_ButtonChrome"></a>
6767
## XAML Object Element Usage
6868
69-
```
69+
```xaml
7070
<theme:ButtonChrome .../>
7171
```
7272
7373
<a name="xamlValues_ButtonChrome"></a>
7474
## XAML Values
75-
`theme:`
75+
`theme:`\
7676
An xmlns prefix for the <xref:Microsoft.Windows.Themes> CLR namespace. Typically, xmlns prefixes and mappings are defined in a XAML root element (not shown).
7777
7878
]]></format>

‎xml/Microsoft.Windows.Themes/ClassicBorderDecorator.xml

+3-3
Original file line numberDiff line numberDiff line change
@@ -32,18 +32,18 @@
3232
<a name="xamlObjectElementUsage_CBD"></a>
3333
## XAML Object Element Usage
3434
35-
```
35+
```xaml
3636
<theme:ClassicBorderDecorator ...>
3737
  singleChild
3838
</theme:ClassicBorderDecorator>
3939
```
4040
4141
<a name="xamlValues_CBD"></a>
4242
## XAML Values
43-
`theme:`
43+
`theme:`\
4444
An xmlns prefix for the <xref:Microsoft.Windows.Themes> CLR namespace. Typically, xmlns prefixes and mappings are defined in a XAML root element (not shown).
4545
46-
*singleChild*
46+
*singleChild*\
4747
A single object element child, representing the object that the border is drawn around. This object must be a <xref:System.Windows.UIElement>. Typical child elements are either a fixed <xref:System.Windows.UIElement> (for example a <xref:System.Windows.Shapes.Path>) or are a presenter or another decorator in compositing.
4848
4949
]]></format>

‎xml/Microsoft.Windows.Themes/DataGridHeaderBorder.xml

+3-3
Original file line numberDiff line numberDiff line change
@@ -81,18 +81,18 @@
8181
<a name="xamlObjectElementUsage_DGHB"></a>
8282
## XAML Object Element Usage
8383
84-
```
84+
```xaml
8585
<theme:DataGridHeaderBorder ...>
8686
  singleChild
8787
</theme:DataGridHeaderBorder>
8888
```
8989
9090
<a name="xamlValues_DGHB"></a>
9191
## XAML Values
92-
`theme:`
92+
`theme:`\
9393
An xmlns prefix for the <xref:Microsoft.Windows.Themes> CLR namespace. Typically, xmlns prefixes and mappings are defined in a XAML root element (not shown).
9494
95-
*singleChild*
95+
*singleChild*\
9696
A single object element child, representing the object that the border is drawn around. This object must be a <xref:System.Windows.UIElement>.
9797
9898
]]></format>

‎xml/Microsoft.Windows.Themes/ListBoxChrome.xml

+3-3
Original file line numberDiff line numberDiff line change
@@ -41,18 +41,18 @@
4141
<a name="xamlObjectElementUsage_LBC"></a>
4242
## XAML Object Element Usage
4343
44-
```
44+
```xaml
4545
<theme:ListBoxChrome ...>
4646
  singleChild
4747
</theme:ListBoxChrome>
4848
```
4949
5050
<a name="xamlValues_LBC"></a>
5151
## XAML Values
52-
`theme:`
52+
`theme:`\
5353
An xmlns prefix for the <xref:Microsoft.Windows.Themes> CLR namespace. Typically, xmlns prefixes and mappings are defined in a XAML root element (not shown).
5454
55-
*singleChild*
55+
*singleChild*\
5656
A single object element child, representing the object that the decorator is drawn around. This object must be a <xref:System.Windows.UIElement>.
5757
5858
]]></format>

‎xml/Microsoft.Windows.Themes/ScrollChrome.xml

+2-2
Original file line numberDiff line numberDiff line change
@@ -73,13 +73,13 @@
7373
<a name="xamlObjectElementUsage_SC"></a>
7474
## XAML Object Element Usage
7575
76-
```
76+
```xaml
7777
<theme:ScrollChrome .../>
7878
```
7979
8080
<a name="xamlValues_SC"></a>
8181
## XAML Values
82-
`theme:`
82+
`theme:`\
8383
An xmlns prefix for the <xref:Microsoft.Windows.Themes> CLR namespace. Typically, xmlns prefixes and mappings are defined in a XAML root element (not shown).
8484
8585
]]></format>

‎xml/System.Activities.Presentation/ActivityDesigner.xml

+2-8
Original file line numberDiff line numberDiff line change
@@ -23,21 +23,16 @@
2323
2424
The <xref:System.Activities.Presentation.ActivityDesigner> inherits from <xref:System.Activities.Presentation.WorkflowViewElement> and primarily adds the default styling, as well as the ability to customize the icon via the <xref:System.Activities.Presentation.ActivityDesigner.Icon%2A> property. It should be used whenever you are creating a designer for a type that derives from <xref:System.Activities.Activity>. When associated with an <xref:System.Activities.Activity> type, the <xref:System.Activities.Presentation.WorkflowViewElement.ModelItem%2A> property will point to the ModelItem hierarchy describing the instance of that type being edited.
2525
26-
27-
2826
## Examples
2927
In the sample code below, a `First2of3` activity is defined first, then the code for the First2of3 designer is shown, and finally it is shown how to use the Designer attribute to associate the activity with the designer is provided.
3028
31-
```
32-
33-
//The First2of3 activity
29+
```csharp
3430
using System.Activities;
3531
using System.Collections.Generic;
3632
using System.Linq;
3733
3834
namespace Microsoft.Activities.Documentation.ActivityTypes
3935
{
40-
4136
public sealed class First2of3 : NativeActivity
4237
{
4338
public Activity Activity1 { get; set; }
@@ -112,10 +107,9 @@ namespace Microsoft.Activities.Documentation.ActivityTypes
112107
</StackPanel>
113108
</sap:ActivityDesigner>
114109
115-
//Code for associating the activity with the designer using the Designer attribute.
110+
// Code for associating the activity with the designer using the Designer attribute.
116111
[Designer(typeof(First2of3Designer))]
117112
public sealed class First2of3 : NativeActivity
118-
119113
```
120114
121115
]]></format>

‎xml/System.ComponentModel.Design/DesignerTransaction.xml

+5-7
Original file line numberDiff line numberDiff line change
@@ -68,28 +68,26 @@
6868
To perform an action within a transaction, you must first create a transaction. Then you must call the <xref:System.ComponentModel.Design.IComponentChangeService.OnComponentChanging%2A> method before each change or set of changes occurs, and the <xref:System.ComponentModel.Design.IComponentChangeService.OnComponentChanged%2A> method after each change or set of changes occur. Finally, complete and close the transaction by calling the <xref:System.ComponentModel.Design.DesignerTransaction.Commit%2A> method.
6969
7070
> [!NOTE]
71-
> When making changes to property values, use the <xref:System.ComponentModel.PropertyDescriptor.SetValue%2A> method of a <xref:System.ComponentModel.PropertyDescriptor>, which calls the component change methods of the <xref:System.ComponentModel.Design.IComponentChangeService> and creates a <xref:System.ComponentModel.Design.DesignerTransaction> representing the change automatically.
71+
> When making changes to property values, use the <xref:System.ComponentModel.PropertyDescriptor.SetValue%2A> method of a <xref:System.ComponentModel.PropertyDescriptor>, which calls the component change methods of the <xref:System.ComponentModel.Design.IComponentChangeService> and creates a <xref:System.ComponentModel.Design.DesignerTransaction> representing the change automatically.
7272
7373
To perform a transaction, complete the following steps:
7474
75-
1. Call <xref:System.ComponentModel.Design.IDesignerHost.CreateTransaction%2A> to obtain a <xref:System.ComponentModel.Design.DesignerTransaction> that can be used to control the transaction.
75+
1. Call <xref:System.ComponentModel.Design.IDesignerHost.CreateTransaction%2A> to obtain a <xref:System.ComponentModel.Design.DesignerTransaction> that can be used to control the transaction.
7676
77-
2. Within a `try` block, for each action that you want to track with a <xref:System.ComponentModel.Design.DesignerTransaction>, call the <xref:System.ComponentModel.Design.IComponentChangeService.OnComponentChanging%2A> method, make the change or changes, then call the <xref:System.ComponentModel.Design.IComponentChangeService.OnComponentChanged%2A> method to signal that the change or changes have been made.
77+
2. Within a `try` block, for each action that you want to track with a <xref:System.ComponentModel.Design.DesignerTransaction>, call the <xref:System.ComponentModel.Design.IComponentChangeService.OnComponentChanging%2A> method, make the change or changes, then call the <xref:System.ComponentModel.Design.IComponentChangeService.OnComponentChanged%2A> method to signal that the change or changes have been made.
7878
79-
3. To complete the transaction, call <xref:System.ComponentModel.Design.DesignerTransaction.Commit%2A> from within a `finally` block.
79+
3. To complete the transaction, call <xref:System.ComponentModel.Design.DesignerTransaction.Commit%2A> from within a `finally` block.
8080
8181
In C#, you can use the `using` statement rather than a `try/finally` block, such as in the following example.
8282
83-
```
83+
```csharp
8484
using (host.CreateTransaction() {
8585
// Insert your code here.
8686
}
8787
```
8888
8989
To cancel and attempt to roll back a transaction before it has been committed, call the <xref:System.ComponentModel.Design.DesignerTransaction.Cancel%2A> method. When the <xref:System.ComponentModel.Design.DesignerTransaction.Cancel%2A> method is invoked, the actions tracked by the <xref:System.ComponentModel.Design.DesignerTransaction> are reversed to attempt to roll back the changes. To undo actions that occurred as part of earlier transactions, you must use the undo command provided by the development environment.
9090
91-
92-
9391
## Examples
9492
The following code example program demonstrates how to create a <xref:System.ComponentModel.Design.DesignerTransaction> from a designer. To run this sample, compile the source code into a class library. You must add a reference to the System.Design assembly. In a new project, add a reference to the compiled DLL and add the component in the library to the **Toolbox**.
9593

‎xml/System.ComponentModel/ICustomTypeDescriptor.xml

+1-1
Original file line numberDiff line numberDiff line change
@@ -925,7 +925,7 @@
925925
926926
This method should return an object that you can use as follows:
927927
928-
```
928+
```csharp
929929
pd.GetValue(GetPropertyOwner(myPd));
930930
```
931931

‎xml/System.IdentityModel.Services.Configuration/FederationConfiguration.xml

+2-2
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@
101101
102102
The `system.identityModel` section must be specified in a `<section>` element under the `<configSections>` element in the configuration file or an exception is thrown.
103103
104-
```
104+
```xml
105105
<configSections>
106106
<section name="system.identityModel" type="System.IdentityModel.Configuration.SystemIdentityModelSection, System.IdentityModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
107107
</configSections>
@@ -147,7 +147,7 @@
147147
148148
Both the `system.identityModel` section and the `system.identityModel.services` must be specified in a `<section>` elements under the `<configSections>` element in the configuration file or an exception is thrown.
149149
150-
```
150+
```xml
151151
<configSections>
152152
<section name="system.identityModel" type="System.IdentityModel.Configuration.SystemIdentityModelSection, System.IdentityModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
153153
<section name="system.identityModel.services" type="System.IdentityModel.Services.Configuration.SystemIdentityModelServicesSection, System.IdentityModel.Services, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />

‎xml/System.IdentityModel.Services/WSFederationAuthenticationModule.xml

+1-1
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@
8686
8787
To be used, the module must be added to the pipeline as in the following XML:
8888
89-
```
89+
```xml
9090
<configuration>
9191
<system.webServer>
9292
<modules>

‎xml/System.Management.Instrumentation/ManagementCreateAttribute.xml

+2-4
Original file line numberDiff line numberDiff line change
@@ -32,14 +32,12 @@
3232
3333
The method parameters should have the same name and type as the parameters of the class binding constructor.
3434
35-
Use of this attribute does not have any affect on registration of the WMI class in the repository. It is only used at runtime.
36-
37-
35+
Use of this attribute does not have any affect on registration of the WMI class in the repository. It is only used at run time.
3836
3937
## Examples
4038
The following example demonstrates how to use the ManagementCreate attribute.
4139
42-
```
40+
```csharp
4341
[ManagementEntity]
4442
public class ProcessInstance
4543
{

‎xml/System.Management.Instrumentation/ManagementEntityAttribute.xml

+9-15
Original file line numberDiff line numberDiff line change
@@ -23,26 +23,20 @@
2323
<Docs>
2424
<summary>The ManagementEntity attribute indicates that a class provides management information exposed through a WMI provider.
2525

26-
Note: the WMI .NET libraries are now considered in final state, and no further development, enhancements, or updates will be available for non-security related issues affecting these libraries. The <see href="https://learn.microsoft.com/previous-versions/windows/desktop/wmi_v2/windows-management-infrastructure">MI APIs</see> should be used for all new development.</summary>
26+
Note: The WMI .NET libraries are now considered in final state, and no further development, enhancements, or updates will be available for non-security related issues affecting these libraries. Use the <see href="/windows/win32/api/_wmi_v2/">MI APIs</see> for all new development.</summary>
2727
<remarks>
2828
<format type="text/markdown"><![CDATA[
2929
3030
## Remarks
3131
The class marked by this attribute must be public.
3232
33-
34-
3533
## Examples
36-
The following example shows how to use the ManagementEntity attribute to mark a class.
3734
38-
```
39-
// Use the ManagementEntity attribute on the class to specify that this // class contains management information that is available from
40-
// provider.
35+
The following example shows how to use the ManagementEntity attribute to mark a class.
4136
42-
[ManagementEntity(Name = "MortgageCalc")]
43-
public class MortgageCalcWMIProvider
44-
{
45-
}
37+
```csharp
38+
[ManagementEntity(Name = "MortgageCalc")]
39+
public class MortgageCalcWMIProvider { }
4640
```
4741
4842
]]></format>
@@ -159,7 +153,7 @@
159153
## Examples
160154
In the following example, the Name parameter is used to set the name of the WMI class represented by the MortgageCalcWMIProvider class. It sets the name to MortgageCalculator. If the Name parameter is not used, the corresponding C# class name, MortgageCalcWMIProvider in this case, is used as the WMI class name.
161155
162-
```
156+
```csharp
163157
[ManagementEntity(Name = "MortgageCalculator")]
164158
public class MortgageCalcWMIProvider
165159
{
@@ -212,12 +206,12 @@ public class MortgageCalcWMIProvider
212206
## Examples
213207
The following code snippet demonstrates how to use the Singleton parameter to indicate that a C# class corresponds to a singleton WMI class.
214208
215-
```
209+
```csharp
216210
[ManagementEntity(Singleton=true)]
217-
public class SingletonSample
211+
public class SingletonSample { }
218212
```
219213
220-
For a complete, working example of a provider that implements a singleton class, see [How to: Create a Basic Decoupled Provider](https://msdn.microsoft.com/library/1dabd442-c1ff-40a1-bb0e-d7b3566c2300).
214+
For a complete, working example of a provider that implements a singleton class, see [How to: Create a Basic Decoupled Provider](/previous-versions/bb885134(v=vs.90)).
221215
222216
]]></format>
223217
</remarks>

‎xml/System.Management.Instrumentation/ManagementNameAttribute.xml

+1-1
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@
3535
## Examples
3636
In the following example, the integer parameter remains i internally, but will be exposed as "The Value" to WMI clients.
3737
38-
```
38+
```csharp
3939
[ManagementTask]
4040
static public int PrintValue([ManagementName("The Value")]int i)
4141
{

‎xml/System.Management.Instrumentation/ManagementQualifierAttribute.xml

+1-1
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@
3737
## Examples
3838
The following example demonstrates using the ManagementQualifier attribute to indicate that a class implements a WMI association class. In this case, the qualifier has a <xref:System.Management.Instrumentation.ManagementQualifierFlavors.DisableOverride> flavor that specifies that the effect of the qualifier cannot be overridden in subclasses.
3939
40-
```
40+
```csharp
4141
[ManagementQualifier("Association", Flavor = ManagementQualifierFlavors.DisableOverride)]
4242
public class AssociationSample
4343
{

‎xml/System.Management.Instrumentation/ManagementQualifierFlavors.xml

+1-1
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@
3434
## Examples
3535
The following example demonstrates how to use the DisableOverride ManagementQualifierFlavors enumeration. Here it is being applied to the Association qualifier.
3636
37-
```
37+
```csharp
3838
[ManagementQualifier("Association",
3939
Flavor = ManagementQualifierFlavors.DisableOverride)]
4040
public class AssociationSampleBase

‎xml/System.Management.Instrumentation/ManagementReferenceAttribute.xml

+1-1
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@
3737
3838
To compile the example, you will need to include references to both System.Management.Instrumentation and System.Configuration.Install. You must run installutil.exe against the resulting executable and ensure that the program is running in order to use the implemented WMI classes.
3939
40-
```
40+
```csharp
4141
using System;
4242
using System.Collections;
4343
using System.Management.Instrumentation;

‎xml/System.Management.Instrumentation/WmiConfigurationAttribute.xml

+6-6
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@
4141
4242
## Examples
4343
44-
```
44+
```csharp
4545
// Specify that this assembly contains code that implements a WMI
4646
// Provider. Use the assembly:WmiConfiguration attribute to define
4747
// the WMI namespace, the hosting model, and the impersonation mode
@@ -129,7 +129,7 @@
129129
## Examples
130130
In the following example, the <xref:System.Management.Instrumentation.WmiConfigurationAttribute> is used to indicate that the assembly it is contained in implements an in-process provider that runs under the NetworkService security context and is hosted in a instance of the Wmiprvse.exe process that also hosts any other in-process providers in the same hosting group that also run within the NetworkService security context.
131131
132-
```
132+
```csharp
133133
[assembly: WmiConfiguration("root\\NVPair", HostingModel = ManagementHostingModel.NetworkService), HostingGroup = "MyProviders"]
134134
```
135135
@@ -179,13 +179,13 @@
179179
## Examples
180180
In the following example, the <xref:System.Management.Instrumentation.WmiConfigurationAttribute> is used to indicate that the assembly it is contained in implements a provider that is exposed through the root\NVPair namespace. Because the hosting model is not <xref:System.Management.Instrumentation.ManagementHostingModel.Decoupled>, it is an in-process provider. The value <xref:System.Management.Instrumentation.ManagementHostingModel.NetworkService> indicates that the in-process provider runs under the NetworkService security context.
181181
182-
```
182+
```csharp
183183
[assembly: WmiConfiguration("root\\NVPair", HostingModel = ManagementHostingModel.NetworkService)]
184184
```
185185
186186
In the next example, the <xref:System.Management.Instrumentation.WmiConfigurationAttribute> is used to indicate that the assembly it is contained in implements a provider that is exposed through the root\NVPair namespace. The value <xref:System.Management.Instrumentation.ManagementHostingModel.Decoupled> indicates that it is a decoupled provider.
187187
188-
```
188+
```csharp
189189
[assembly: WmiConfiguration("root\\NVPair", HostingModel = ManagementHostingModel.Decoupled)]
190190
```
191191
@@ -231,7 +231,7 @@
231231
## Examples
232232
The following example demonstrates how to use the IdentifyLevel parameter to indicate that the provider can impersonate its callers.
233233
234-
```
234+
```csharp
235235
[assembly: WmiConfiguration("root/MyProv", HostingModel = ManagementHostingModel.Decoupled, IdentifyLevel = true]
236236
```
237237
@@ -277,7 +277,7 @@
277277
## Examples
278278
The following example demonstrates how to use the NamespaceSecurity parameter to set the security descriptor on the root/SDTest namespace in which the provider implemented in this assembly exposes WMI classes.
279279
280-
```
280+
```csharp
281281
[assembly: WmiConfiguration("root/SDTest", HostingModel = ManagementHostingModel.Decoupled, IdentifyLevel = false, NamespaceSecurity = "O:BAG:BAD:(A;CI;0x60003;;;WD)")]
282282
```
283283

0 commit comments

Comments
 (0)