Merge main into live

.github/policies/close-issues.yml

@@ -1,14 +1,97 @@
 name: Close issues
-description: Close issues based on label.
+description: Close issues based on label
 resource: repository
 where:
 configuration:
     resourceManagementConfiguration:
-        eventResponderTasks:              
+        scheduledSearches:
+          - frequencies:
+            - daily:
+                time: 12:00
+            filters:
+              - isIssue
+              - isOpen
+              - hasLabel:
+                  label: needs-more-info
+              - noActivitySince:
+                  days: 14
+            actions:
+              - addReply:
+                  reply: This issue has been automatically closed due to no response from the original author. Feel free to reopen it if you have more information that can help us investigate the issue further.
+              - closeIssue
+
+        eventResponderTasks:
+          - description: Remove needs-more-info label when author comments on issue
+            if:
+              - payloadType: Issue_Comment
+              - isAction:
+                  action: Created
+              - isActivitySender:
+                  issueAuthor: True
+              - hasLabel:
+                  label: needs-more-info
+              - isOpen
+            then:
+              - removeLabel:
+                  label: needs-more-info
+            triggerOnOwnActions: true
+
           - description: Close issues labeled 'code-of-conduct'
             if:
               - payloadType: Issues
               - hasLabel:
                   label: code-of-conduct
             then:
               - closeIssue
+
+          - description: Close learn template issues with empty descriptions (spam).
+            if:
+              - payloadType: Issues
+              - or:
+                - bodyContains:
+                    pattern: '### Description[\n\r]+\[Enter feedback here\][\n\r]+###'
+                    isRegex: True
+                - bodyContains:
+                    pattern: '### Description[\n\r]+\[Escriba sus comentarios aquí][\n\r]+###'
+                    isRegex: True
+                - bodyContains:
+                    pattern: '### Description[\n\r]+\[Tapez vos commentaires ici][\n\r]+###'
+                    isRegex: True
+                - bodyContains:
+                    pattern: '### Description[\n\r]+\[Hier Feedback eingeben][\n\r]+###'
+                    isRegex: true
+                - bodyContains:
+                    pattern: '### Description[\n\r]+\[Geri bildiriminizi buraya girin][\n\r]+###'
+                    isRegex: True
+                - bodyContains:
+                    pattern: '### Description[\n\r]+\[Ketikkan umpan balik di sini][\n\r]+###'
+                    isRegex: True
+                - bodyContains:
+                    pattern: '### Description[\n\r]+\[Immetti qui i commenti][\n\r]+###'
+                    isRegex: True
+                - bodyContains:
+                    pattern: '### Description[\n\r]+\[Voer hier feedback in][\n\r]+###'
+                    isRegex: True
+                - bodyContains:
+                    pattern: '### Description[\n\r]+\[Insira comentários aqui][\n\r]+###'
+                    isRegex: True
+                - bodyContains:
+                    pattern: '### Description[\n\r]+\[Введите отзыв здесь][\n\r]+###'
+                    isRegex: True
+                - bodyContains:
+                    pattern: '### Description[\n\r]+\[اكتب ملاحظاتك هنا][\n\r]+###'
+                    isRegex: True
+                - bodyContains:
+                    pattern: '### Description[\n\r]+\[在此处输入反馈][\n\r]+###'
+                    isRegex: True
+                - bodyContains:
+                    pattern: '### Description[\n\r]+\[여기에 피드백 입력][\n\r]+###'
+                    isRegex: True
+                - bodyContains:
+                    pattern: '### Description[\n\r]+\[フィードバックをこちらに入力してください][\n\r]+###'
+                    isRegex: True
+            then:
+              - addLabel: 'needs-more-info'
+              - addReply:
+                  reply: This issue has been automatically closed due to an empty issue description from the original author. Feel free to reopen it if you have more information that can help us investigate the issue further.
+              - closeIssue

.openpublishing.publish.config.json

@@ -56,7 +56,7 @@
   "git_repository_branch_open_to_public_contributors": "main",
   "skip_source_output_uploading": false,
   "need_preview_pull_request": true,
-  "need_pr_comments": true,
+  "need_pr_comments": false,
   "contribution_branch_mappings": {},
   "dependent_repositories": [
     {
@@ -100,4 +100,4 @@
       "version": "latest"
     }
   ]
-}
+}

xml/Microsoft.Extensions.Configuration.Ini/IniConfigurationProvider.xml

@@ -43,7 +43,7 @@
 
 INI files are simple line structures ([INI Files on Wikipedia](https://en.wikipedia.org/wiki/INI_file)). The following example demonstrates a structure of the INI file:
 
-```
+```ini
 [Section:Header]
 key1=value1
 key2 = " value2 "

xml/Microsoft.Extensions.Http/PolicyHttpMessageHandler.xml

@@ -36,8 +36,8 @@ The <xref:Microsoft.Extensions.DependencyInjection.PollyHttpClientBuilderExtensi
 <xref:Microsoft.Extensions.Http.PolicyHttpMessageHandler> and the <xref:Microsoft.Extensions.DependencyInjection.PollyHttpClientBuilderExtensions> convenience methods only accept the generic <xref:Polly.IAsyncPolicy`1>. Generic policy instances can be created by using the generic methods on <xref:Polly.Policy> such as <xref:Polly.Policy.TimeoutAsync``1(System.Int32)>.
 
 To adapt an existing non-generic <xref:Polly.IAsyncPolicy>, use code like the following:
-        
-```
+
+```csharp
 policy.AsAsyncPolicy&lt;HttpResponseMessage&gt;()
 ```
 

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

@@ -933,7 +933,7 @@
 
  The `Path` property can also be set to a qualified network path without a drive connection using the following syntax:
 
-```
+```txt
 \\servername\sharename\path
 ```
 

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

@@ -696,7 +696,7 @@
 
  The `Path` property can also be set to a qualified network path without a drive connection using the following syntax:
 
-```
+```txt
 \\servername\sharename\path
 ```
 

xml/Microsoft.Windows.Themes/BulletChrome.xml

@@ -66,13 +66,14 @@
 <a name="xamlObjectElementUsage_BulletChrome"></a>
 ## XAML Object Element Usage
 
-```
+```xaml
 <theme:BulletChrome .../>
 ```
 
 <a name="xamlValues_BulletChrome"></a>
 ## XAML Values
- `theme:`
+
+ `theme:`\
  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).
 
  ]]></format>

xml/Microsoft.Windows.Themes/ButtonChrome.xml

@@ -66,13 +66,13 @@
 <a name="xamlObjectElementUsage_ButtonChrome"></a>
 ## XAML Object Element Usage
 
-```
+```xaml
 <theme:ButtonChrome .../>
 ```
 
 <a name="xamlValues_ButtonChrome"></a>
 ## XAML Values
- `theme:`
+ `theme:`\
  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).
 
  ]]></format>

xml/Microsoft.Windows.Themes/ClassicBorderDecorator.xml

@@ -32,18 +32,18 @@
 <a name="xamlObjectElementUsage_CBD"></a>
 ## XAML Object Element Usage
 
-```
+```xaml
 <theme:ClassicBorderDecorator ...>
   singleChild
 </theme:ClassicBorderDecorator>
 ```
 
 <a name="xamlValues_CBD"></a>
 ## XAML Values
- `theme:`
+ `theme:`\
  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).
 
- *singleChild*
+ *singleChild*\
  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.
 
  ]]></format>

xml/Microsoft.Windows.Themes/DataGridHeaderBorder.xml

@@ -81,18 +81,18 @@
 <a name="xamlObjectElementUsage_DGHB"></a>
 ## XAML Object Element Usage
 
-```
+```xaml
 <theme:DataGridHeaderBorder ...>
   singleChild
 </theme:DataGridHeaderBorder>
 ```
 
 <a name="xamlValues_DGHB"></a>
 ## XAML Values
- `theme:`
+ `theme:`\
  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).
 
- *singleChild*
+ *singleChild*\
  A single object element child, representing the object that the border is drawn around. This object must be a <xref:System.Windows.UIElement>.
 
  ]]></format>

xml/Microsoft.Windows.Themes/ListBoxChrome.xml

@@ -41,18 +41,18 @@
 <a name="xamlObjectElementUsage_LBC"></a>
 ## XAML Object Element Usage
 
-```
+```xaml
 <theme:ListBoxChrome ...>
   singleChild
 </theme:ListBoxChrome>
 ```
 
 <a name="xamlValues_LBC"></a>
 ## XAML Values
- `theme:`
+ `theme:`\
  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).
 
- *singleChild*
+ *singleChild*\
  A single object element child, representing the object that the decorator is drawn around. This object must be a <xref:System.Windows.UIElement>.
 
  ]]></format>

xml/Microsoft.Windows.Themes/ScrollChrome.xml

@@ -73,13 +73,13 @@
 <a name="xamlObjectElementUsage_SC"></a>
 ## XAML Object Element Usage
 
-```
+```xaml
 <theme:ScrollChrome .../>
 ```
 
 <a name="xamlValues_SC"></a>
 ## XAML Values
- `theme:`
+ `theme:`\
  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).
 
  ]]></format>

xml/System.Activities.Presentation/ActivityDesigner.xml

@@ -23,21 +23,16 @@
 
  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.
 
-
-
 ## Examples
  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.
 
-```
-
-//The First2of3 activity
+```csharp
 using System.Activities;
 using System.Collections.Generic;
 using System.Linq;
 
 namespace Microsoft.Activities.Documentation.ActivityTypes
 {
-
     public sealed class First2of3 : NativeActivity
     {
         public Activity Activity1 { get; set; }
@@ -112,10 +107,9 @@ namespace Microsoft.Activities.Documentation.ActivityTypes
     </StackPanel>
 </sap:ActivityDesigner>
 
-//Code for associating the activity with the designer using the Designer attribute.
+// Code for associating the activity with the designer using the Designer attribute.
 [Designer(typeof(First2of3Designer))]
 public sealed class First2of3 : NativeActivity
-
 ```
 
  ]]></format>

xml/System.ComponentModel.Design/DesignerTransaction.xml

@@ -68,28 +68,26 @@
  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.
 
 > [!NOTE]
->  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.
+> 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.
 
  To perform a transaction, complete the following steps:
 
-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.
+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.
 
-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.
+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.
 
-3.  To complete the transaction, call <xref:System.ComponentModel.Design.DesignerTransaction.Commit%2A> from within a `finally` block.
+3. To complete the transaction, call <xref:System.ComponentModel.Design.DesignerTransaction.Commit%2A> from within a `finally` block.
 
  In C#, you can use the `using` statement rather than a `try/finally` block, such as in the following example.
 
-```
+```csharp
 using (host.CreateTransaction() {
 // Insert your code here.
 }
 ```
 
  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.
 
-
-
 ## Examples
  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**.
 

xml/System.ComponentModel/ICustomTypeDescriptor.xml

@@ -925,7 +925,7 @@
 
  This method should return an object that you can use as follows:
 
-```
+```csharp
 pd.GetValue(GetPropertyOwner(myPd));
 ```