Merge main into live

snippets/csharp/System.Numerics/BigInteger/.ctor/Example1.cs

@@ -1,7 +1,7 @@
 using System;
 using System.Numerics;
 
-public class Example
+public class Example1
 {
    public static void Main()
    {

snippets/csharp/System.Numerics/BigInteger/.ctor/Example2.cs

@@ -1,7 +1,7 @@
 using System;
 using System.Numerics;
 
-public class Example
+public class Example2
 {
    public static void Main()
    {
@@ -98,13 +98,13 @@ private static void LongConstructor()
                            constructed.Equals(assigned));
       }
       // The example displays the following output:
-      //       -2147483648 = -2147483648: True
+      //       -9223372036854775808 = -9223372036854775808: True
       //       -10534 = -10534: True
       //       -189 = -189: True
       //       0 = 0: True
       //       17 = 17: True
       //       113439 = 113439: True
-      //       2147483647 = 2147483647: True
+      //       9223372036854775807 = 9223372036854775807: True
       // </Snippet7>
    }
 

snippets/csharp/System.Numerics/BigInteger/.ctor/Project.csproj

@@ -0,0 +1,6 @@
+<Project Sdk="Microsoft.NET.Sdk">
+  <PropertyGroup>
+    <OutputType>Library</OutputType>
+    <TargetFramework>net9.0</TargetFramework>
+  </PropertyGroup>
+</Project>

snippets/fsharp/System.Numerics/BigInteger/.ctor/Example2.fs

@@ -63,13 +63,13 @@ let longConstructor () =
         let assigned = number
         printfn $"{constructed} = {assigned}: {constructed.Equals assigned}"
     // The example displays the following output:
-    //       -2147483648 = -2147483648: True
+    //       -9223372036854775808 = -9223372036854775808: True
     //       -10534 = -10534: True
     //       -189 = -189: True
     //       0 = 0: True
     //       17 = 17: True
     //       113439 = 113439: True
-    //       2147483647 = 2147483647: True
+    //       9223372036854775807 = 9223372036854775807: True
     // </Snippet7>
 
 let singleConstructor () =

snippets/visualbasic/VS_Snippets_CLR_System/system.Numerics.BigInteger.ctors/vb/Example1.vb

@@ -3,7 +3,7 @@ Option Strict On
 
 Imports System.Numerics
 
-Module Example
+Module Example1
    Public Sub Main()
       Console.WindowWidth = 90
       CreateSimpleArray()

snippets/visualbasic/VS_Snippets_CLR_System/system.Numerics.BigInteger.ctors/vb/Example2.vb

@@ -3,7 +3,7 @@ Option Strict On
 
 Imports System.Numerics
 
-Module Example
+Module Example2
    Public Sub Main()
       DecimalConstructor()
       Console.WriteLine("-----")
@@ -92,13 +92,13 @@ Module Example
                            constructed.Equals(assigned)) 
       Next
       ' The example displays the following output:
-      '       -2147483648 = -2147483648: True
+      '       -9223372036854775808 = -9223372036854775808: True
       '       -10534 = -10534: True
       '       -189 = -189: True
       '       0 = 0: True
       '       17 = 17: True
       '       113439 = 113439: True
-      '       2147483647 = 2147483647: True
+      '       9223372036854775807 = 9223372036854775807: True
       ' </Snippet7>
    End Sub   
 

snippets/visualbasic/VS_Snippets_CLR_System/system.Numerics.BigInteger.ctors/vb/Project.vbproj

@@ -0,0 +1,7 @@
+<Project Sdk="Microsoft.NET.Sdk">
+  <PropertyGroup>
+    <OutputType>Library</OutputType>
+    <TargetFramework>net9.0</TargetFramework>
+
+  </PropertyGroup>
+</Project>

xml/System.Security.Cryptography.X509Certificates/X509Chain.xml

@@ -78,7 +78,7 @@
 >   
 >  For apps that target the .NET Framework 4.5.2 and earlier versions, the <xref:System.Security.Cryptography.X509Certificates.X509Chain> class does not implement the <xref:System.IDisposable> interface and therefore does not have a `Dispose` method.  
 
-   
+ When disposing <xref:System.Security.Cryptography.X509Certificates.X509Chain>, the certificates in <xref:System.Security.Cryptography.X509Certificates.X509Chain.ChainElements> are not disposed. You should dispose of the certificates in this collection when the certificate instances are no longer needed.
 
 ## Examples  
  The following code example opens the current user's personal certificate store, allows you to select a certificate, then writes certificate and certificate chain information to the console. The output depends on the certificate you select.  

xml/System/AppDomain.xml

@@ -94,7 +94,6 @@
 Application domains, which are represented by <xref:System.AppDomain> objects, help provide isolation, unloading, and security boundaries for executing managed code.
 
 - Use application domains to isolate tasks that might bring down a process. If the state of the <xref:System.AppDomain> that's executing a task becomes unstable, the <xref:System.AppDomain> can be unloaded without affecting the process. This is important when a process must run for long periods without restarting. You can also use application domains to isolate tasks that should not share data.
-
 - If an assembly is loaded into the default application domain, it cannot be unloaded from memory while the process is running. However, if you open a second application domain to load and execute the assembly, the assembly is unloaded when that application domain is unloaded. Use this technique to minimize the working set of long-running processes that occasionally use large DLLs.
 
  > [!NOTE]
@@ -5886,9 +5885,8 @@ This method overload uses the <xref:System.AppDomainSetup> information from the
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The friendly name of the default application domain is the file name of the process executable. For example, if the executable used to start the process is `"c:\MyAppDirectory\MyAssembly.exe"`, the friendly name of the default application domain is `"MyAssembly.exe"`.
-
 
+The friendly name of the default application domain is the file name of the process executable. For example, if the executable used to start the process is `"c:\MyAppDirectory\MyAssembly.exe"`, the friendly name of the default application domain is `"MyAssembly.exe"`. (In .NET Core and .NET 5+, the friendly name doesn't include the file extension.)
 
 ## Examples
  The following code example uses the <xref:System.AppDomain.FriendlyName%2A> property to get the friendly name of the current application domain. For the default application domain, the friendly name is the name of the application's executable file. The code example also displays additional information about the application domain.