Merge main into live

xml/FrameworksIndex/windowsdesktop-10.0.xml

@@ -12350,10 +12350,12 @@
       <Member Id="M:System.Security.Cryptography.Pkcs.CmsSigner.#ctor(System.Security.Cryptography.Pkcs.SubjectIdentifierType,System.Security.Cryptography.X509Certificates.X509Certificate2)" />
       <Member Id="M:System.Security.Cryptography.Pkcs.CmsSigner.#ctor(System.Security.Cryptography.Pkcs.SubjectIdentifierType,System.Security.Cryptography.X509Certificates.X509Certificate2,System.Security.Cryptography.AsymmetricAlgorithm)" />
       <Member Id="M:System.Security.Cryptography.Pkcs.CmsSigner.#ctor(System.Security.Cryptography.Pkcs.SubjectIdentifierType,System.Security.Cryptography.X509Certificates.X509Certificate2,System.Security.Cryptography.RSA,System.Security.Cryptography.RSASignaturePadding)" />
+      <Member Id="M:System.Security.Cryptography.Pkcs.CmsSigner.#ctor(System.Security.Cryptography.Pkcs.SubjectIdentifierType,System.Security.Cryptography.X509Certificates.X509Certificate2,System.Security.Cryptography.SlhDsa)" />
       <Member Id="M:System.Security.Cryptography.Pkcs.CmsSigner.#ctor(System.Security.Cryptography.X509Certificates.X509Certificate2)" />
       <Member Id="P:System.Security.Cryptography.Pkcs.CmsSigner.Certificate" />
       <Member Id="P:System.Security.Cryptography.Pkcs.CmsSigner.Certificates" />
       <Member Id="P:System.Security.Cryptography.Pkcs.CmsSigner.DigestAlgorithm" />
+      <Member Id="P:System.Security.Cryptography.Pkcs.CmsSigner.HasPrivateKey" />
       <Member Id="P:System.Security.Cryptography.Pkcs.CmsSigner.IncludeOption" />
       <Member Id="P:System.Security.Cryptography.Pkcs.CmsSigner.PrivateKey" />
       <Member Id="P:System.Security.Cryptography.Pkcs.CmsSigner.SignaturePadding" />
@@ -35817,6 +35819,9 @@
       <Member Id="P:System.Windows.Forms.HtmlWindowCollection.System#Collections#ICollection#IsSynchronized" />
       <Member Id="P:System.Windows.Forms.HtmlWindowCollection.System#Collections#ICollection#SyncRoot" />
     </Type>
+    <Type Name="System.Windows.Forms.IAsyncDropTarget" Id="T:System.Windows.Forms.IAsyncDropTarget">
+      <Member Id="M:System.Windows.Forms.IAsyncDropTarget.OnAsyncDragDrop(System.Windows.Forms.DragEventArgs)" />
+    </Type>
     <Type Name="System.Windows.Forms.IBindableComponent" Id="T:System.Windows.Forms.IBindableComponent">
       <Member Id="P:System.Windows.Forms.IBindableComponent.BindingContext" />
       <Member Id="P:System.Windows.Forms.IBindableComponent.DataBindings" />

xml/Microsoft.Extensions.VectorData/VectorStore.xml

@@ -214,9 +214,9 @@
             To successfully request a collection, either <typeparamref name="TRecord" /> must be annotated with attributes that define the schema of
             the record type, or <paramref name="definition" /> must be provided.
             </remarks>
+        <altmember cref="T:Microsoft.Extensions.VectorData.VectorStoreVectorAttribute" />
         <altmember cref="T:Microsoft.Extensions.VectorData.VectorStoreKeyAttribute" />
         <altmember cref="T:Microsoft.Extensions.VectorData.VectorStoreDataAttribute" />
-        <altmember cref="T:Microsoft.Extensions.VectorData.VectorStoreVectorAttribute" />
       </Docs>
     </Member>
     <Member MemberName="GetDynamicCollection">

xml/System.CodeDom.Compiler/CodeDomProvider.xml

@@ -49,9 +49,6 @@
 ## Remarks
  A <xref:System.CodeDom.Compiler.CodeDomProvider> can be used to create and retrieve instances of code generators and code compilers. Code generators can be used to generate code in a particular language, and code compilers can be used to compile code into assemblies.
 
-> [!NOTE]
->  In the .NET Framework 2.0, the methods made available in the code generator and code compiler are available directly from the code provider. You do not need to call <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A> or <xref:System.CodeDom.Compiler.CodeDomProvider.CreateCompiler%2A> to access the methods, and those methods are marked as obsolete. This applies to preexisting as well as new code provider implementations.
-
  A <xref:System.CodeDom.Compiler.CodeDomProvider> implementation typically provides code generation and/or code compilation interfaces for generating code and managing compilation for a single programming language. Several languages are supported by <xref:System.CodeDom.Compiler.CodeDomProvider> implementations that ship with the Windows SDK. These languages include C#, Visual Basic, C++, and JScript. Developers or compiler vendors can implement the <xref:System.CodeDom.Compiler.ICodeGenerator> and <xref:System.CodeDom.Compiler.ICodeCompiler> interfaces and provide a <xref:System.CodeDom.Compiler.CodeDomProvider> that extends CodeDOM support to other programming languages.
 
  The [&lt;system.codedom&gt; Element](/dotnet/framework/configure-apps/file-schema/compiler/system-codedom-element) in the machine configuration file (Machine.config) provides a mechanism for developers and compiler vendors to add configuration settings for additional <xref:System.CodeDom.Compiler.CodeDomProvider> implementations.
@@ -74,7 +71,7 @@
  ]]></format>
     </remarks>
     <block subset="none" type="overrides">
-      <para>In the .NET Framework versions 1.0 and 1.1, code providers consist of implementations of <see cref="T:System.CodeDom.Compiler.CodeDomProvider" />, <see cref="T:System.CodeDom.Compiler.ICodeGenerator" />, <see cref="T:System.CodeDom.Compiler.ICodeParser" />, and <see cref="T:System.CodeDom.Compiler.ICodeCompiler" />. In the .NET Framework 2.0, the <see cref="M:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator" />, <see cref="M:System.CodeDom.Compiler.CodeDomProvider.CreateParser" />, and <see cref="M:System.CodeDom.Compiler.CodeDomProvider.CreateCompiler" /> methods are obsolete, and the methods of <see cref="T:System.CodeDom.Compiler.ICodeGenerator" /> and <see cref="T:System.CodeDom.Compiler.ICodeCompiler" /> are directly available in the <see cref="T:System.CodeDom.Compiler.CodeDomProvider" /> class. You should override those methods in your code provider implementation and not call the base methods.</para>
+      <para>In .NET Framework 1.0 and 1.1, code providers consist of implementations of <see cref="T:System.CodeDom.Compiler.CodeDomProvider" />, <see cref="T:System.CodeDom.Compiler.ICodeGenerator" />, <see cref="T:System.CodeDom.Compiler.ICodeParser" />, and <see cref="T:System.CodeDom.Compiler.ICodeCompiler" />. Starting in .NET Framework 2.0, the <see cref="M:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator" />, <see cref="M:System.CodeDom.Compiler.CodeDomProvider.CreateParser" />, and <see cref="M:System.CodeDom.Compiler.CodeDomProvider.CreateCompiler" /> methods are obsolete, and the methods of <see cref="T:System.CodeDom.Compiler.ICodeGenerator" /> and <see cref="T:System.CodeDom.Compiler.ICodeCompiler" /> are directly available in the <see cref="T:System.CodeDom.Compiler.CodeDomProvider" /> class. You should override those methods in your code provider implementation and not call the base methods.</para>
     </block>
     <altmember cref="T:System.CodeDom.Compiler.CompilerInfo" />
     <altmember cref="T:Microsoft.CSharp.CSharpCodeProvider" />
@@ -171,7 +168,7 @@
 > On .NET Core and .NET 5+, calls to the `CodeDomProvider.CompileAssemblyFromDom` method throw a <xref:System.PlatformNotSupportedException>. Compile code is not supported.
 
 > [!NOTE]
->  In .NET Framework 2.0 and later versions, this method can be called directly on the code provider even if it's not overridden by the code provider. If the code provider does not override this method, the <xref:System.CodeDom.Compiler.ICodeCompiler> implementation is called by the base class.
+> In .NET Framework 2.0 and later versions, this method can be called directly on the code provider even if it's not overridden by the code provider. If the code provider does not override this method, the <xref:System.CodeDom.Compiler.ICodeCompiler> implementation is called by the base class.
 
  ]]></format>
         </remarks>
@@ -361,12 +358,12 @@
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- This method is obsolete in the .NET Framework 2.0. The recommended alternative is to call the <xref:System.CodeDom.Compiler.ICodeCompiler> methods that are directly available in the code provider.
+ This method is obsolete. The recommended alternative is to call the <xref:System.CodeDom.Compiler.ICodeCompiler> methods that are directly available in the code provider.
 
  ]]></format>
         </remarks>
         <block subset="none" type="overrides">
-          <para>In the .NET Framework 2.0, you should implement the <see cref="T:System.CodeDom.Compiler.ICodeCompiler" /> members in the <see cref="T:System.CodeDom.Compiler.CodeDomProvider" /> class and throw a <see cref="T:System.NotSupportedException" /> when this method is called.</para>
+          <para>You should implement the <see cref="T:System.CodeDom.Compiler.ICodeCompiler" /> members in the <see cref="T:System.CodeDom.Compiler.CodeDomProvider" /> class and throw a <see cref="T:System.NotSupportedException" /> when this method is called.</para>
         </block>
       </Docs>
     </Member>
@@ -476,12 +473,12 @@
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- This method is obsolete in the .NET Framework 2.0. The recommended alternative is to call the <xref:System.CodeDom.Compiler.ICodeGenerator> methods that are directly available in the <xref:System.CodeDom.Compiler.CodeDomProvider> class.
+ This method is obsolete. The recommended alternative is to call the <xref:System.CodeDom.Compiler.ICodeGenerator> methods that are directly available in the <xref:System.CodeDom.Compiler.CodeDomProvider> class.
 
  ]]></format>
         </remarks>
         <block subset="none" type="overrides">
-          <para>In the .NET Framework 2.0, you should implement the <see cref="T:System.CodeDom.Compiler.ICodeGenerator" /> members in the <see cref="T:System.CodeDom.Compiler.CodeDomProvider" /> class and throw a <see cref="T:System.NotSupportedException" /> when this method is called.</para>
+          <para>You should implement the <see cref="T:System.CodeDom.Compiler.ICodeGenerator" /> members in the <see cref="T:System.CodeDom.Compiler.CodeDomProvider" /> class and throw a <see cref="T:System.NotSupportedException" /> when this method is called.</para>
         </block>
       </Docs>
     </Member>
@@ -533,7 +530,7 @@
  This method uses the specified <xref:System.IO.TextWriter> for output. This method supports more optimized code generation that incrementally updates the source code.
 
 > [!NOTE]
->  The base class implementation calls the <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A> method, which is obsolete in the .NET Framework 2.0 and results in a <xref:System.NotSupportedException> if an <xref:System.CodeDom.Compiler.ICodeGenerator> object is not returned.
+> The base class implementation calls the <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A> method, which is obsolete and results in a <xref:System.NotSupportedException> if an <xref:System.CodeDom.Compiler.ICodeGenerator> object is not returned.
 
  ]]></format>
         </remarks>
@@ -588,7 +585,7 @@
  This method uses the specified file name for output.
 
 > [!NOTE]
->  The base class implementation calls the <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A> method, which is obsolete in the .NET Framework 2.0 and results in a <xref:System.NotSupportedException> if an <xref:System.CodeDom.Compiler.ICodeGenerator> object is not returned.
+> The base class implementation calls the <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A> method, which is obsolete and results in a <xref:System.NotSupportedException> if an <xref:System.CodeDom.Compiler.ICodeGenerator> object is not returned.
 
  ]]></format>
         </remarks>
@@ -1287,11 +1284,6 @@
 ## Remarks
  Use the <xref:System.CodeDom.Compiler.CodeDomProvider.GetAllCompilerInfo%2A> method to enumerate the language provider settings on a computer.
 
-> [!NOTE]
->  In the .NET Framework 2.0, the default language providers supplied by the .NET Framework are not specified in the [&lt;system.codedom&gt; Element](/dotnet/framework/configure-apps/file-schema/compiler/system-codedom-element) compiler configuration section and cannot be removed, so this method returns information about the default providers and any specified in the configuration file.
-
-
-
 ## Examples
  The following code example enumerates the language providers on the computer and displays the configuration and compiler settings for each language provider. This code example is part of a larger example provided for the <xref:System.CodeDom.Compiler.CompilerInfo> class.
 

xml/System.CodeDom.Compiler/ICodeCompiler.xml

@@ -31,19 +31,19 @@
   <Docs>
     <summary>Defines an interface for invoking compilation of source code or a CodeDOM tree using a specific compiler.</summary>
     <remarks>
-      <format type="text/markdown"><![CDATA[  
-  
-## Remarks  
-  
+      <format type="text/markdown"><![CDATA[
+
+## Remarks
+
 > [!NOTE]
->  In the .NET Framework versions 1.0 and 1.1, code providers consist of implementations of <xref:System.CodeDom.Compiler.CodeDomProvider>, <xref:System.CodeDom.Compiler.ICodeGenerator>, <xref:System.CodeDom.Compiler.ICodeParser>, and <xref:System.CodeDom.Compiler.ICodeCompiler>. In the .NET Framework 2.0, the <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A>, <xref:System.CodeDom.Compiler.CodeDomProvider.CreateParser%2A>, and <xref:System.CodeDom.Compiler.CodeDomProvider.CreateCompiler%2A> methods are obsolete, and the methods of <xref:System.CodeDom.Compiler.ICodeGenerator> and <xref:System.CodeDom.Compiler.ICodeCompiler> are directly available in the <xref:System.CodeDom.Compiler.CodeDomProvider> class. You should override those methods in your code provider implementation and not call the base methods.  
-  
- The <xref:System.CodeDom.Compiler.ICodeCompiler> interface can be implemented for a specific compiler to enable developers to programmatically compile assemblies from Code Document Object Model (CodeDOM) compile units, strings containing source code, or source code files.  
-  
- The <xref:System.CodeDom.Compiler.ICodeCompiler> interface provides the capability to invoke compilation with specified parameters at runtime and access information related to compilation after compilation occurs, including the result code, and any errors or warnings the compiler returns. Each compile method accepts a <xref:System.CodeDom.Compiler.CompilerParameters> object that indicates settings for the compiler, and returns a <xref:System.CodeDom.Compiler.CompilerResults> object that indicates the results of the compilation.  
-  
- Compiler developers should provide an implementation of this interface to support dynamic compilation. <xref:System.CodeDom.Compiler.CodeDomProvider> implementers should also consider implementing this interface to provide programmatic compilation capability for the language that they are providing CodeDom support for.  
-  
+> Starting in .NET Framework 2.0, the <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A>, <xref:System.CodeDom.Compiler.CodeDomProvider.CreateParser%2A>, and <xref:System.CodeDom.Compiler.CodeDomProvider.CreateCompiler%2A> methods are obsolete, and the methods of <xref:System.CodeDom.Compiler.ICodeGenerator> and <xref:System.CodeDom.Compiler.ICodeCompiler> are directly available in the <xref:System.CodeDom.Compiler.CodeDomProvider> class. You should override those methods in your code provider implementation and not call the base methods.
+
+ The <xref:System.CodeDom.Compiler.ICodeCompiler> interface can be implemented for a specific compiler to enable developers to programmatically compile assemblies from Code Document Object Model (CodeDOM) compile units, strings containing source code, or source code files.
+
+ The <xref:System.CodeDom.Compiler.ICodeCompiler> interface provides the capability to invoke compilation with specified parameters at runtime and access information related to compilation after compilation occurs, including the result code, and any errors or warnings the compiler returns. Each compile method accepts a <xref:System.CodeDom.Compiler.CompilerParameters> object that indicates settings for the compiler, and returns a <xref:System.CodeDom.Compiler.CompilerResults> object that indicates the results of the compilation.
+
+ Compiler developers should provide an implementation of this interface to support dynamic compilation. <xref:System.CodeDom.Compiler.CodeDomProvider> implementers should also consider implementing this interface to provide programmatic compilation capability for the language that they are providing CodeDom support for.
+
  ]]></format>
     </remarks>
     <altmember cref="T:System.CodeDom.Compiler.CompilerParameters" />