Merge main into live

.github/workflows/cleanrepo-orphaned-articles.yml

@@ -35,7 +35,7 @@
 
       # Create the PR for the work done by the "clean repo" tool
       - name: create-pull-request
-        uses: dotnet/actions-create-pull-request@v4
+        uses: peter-evans/create-pull-request@v7
         with:
           branch: cleanrepo-orphaned-articles
           title: "Monthly chores: Delete orphaned articles"

.github/workflows/cleanrepo-orphaned-images.yml

@@ -35,7 +35,7 @@
 
       # Create the PR for the work done by the "clean repo" tool
       - name: create-pull-request
-        uses: dotnet/actions-create-pull-request@v4
+        uses: peter-evans/create-pull-request@v7
         with:
           branch: cleanrepo-orphaned-images
           title: "Monthly chores: Delete orphaned images"

.github/workflows/cleanrepo-orphaned-includes.yml

@@ -35,7 +35,7 @@
 
       # Create the PR for the work done by the "clean repo" tool
       - name: create-pull-request
-        uses: dotnet/actions-create-pull-request@v4
+        uses: peter-evans/create-pull-request@v7
         with:
           branch: cleanrepo-orphaned-includes
           title: "Monthly chores: Delete orphaned include files"

.github/workflows/cleanrepo-orphaned-snippets.yml

@@ -35,7 +35,7 @@
 
       # Create the PR for the work done by the "clean repo" tool
       - name: create-pull-request
-        uses: dotnet/actions-create-pull-request@v4
+        uses: peter-evans/create-pull-request@v7
         with:
           branch: cleanrepo-orphaned-snippets
           title: "Monthly chores: Delete orphaned snippets"

.github/workflows/cleanrepo-redirect-hops.yml

@@ -35,7 +35,7 @@
 
       # Create the PR for the work done by the "clean repo" tool
       - name: create-pull-request
-        uses: dotnet/actions-create-pull-request@v4
+        uses: peter-evans/create-pull-request@v7
         with:
           branch: cleanrepo-remove-hops
           title: "Monthly chores: Remove redirect hops"

.github/workflows/cleanrepo-relative-links.yml

@@ -35,7 +35,7 @@
 
       # Create the PR for the work done by the "clean repo" tool
       - name: create-pull-request
-        uses: dotnet/actions-create-pull-request@v4
+        uses: peter-evans/create-pull-request@v7
         with:
           branch: cleanrepo-relative-links
           title: "Monthly chores: Use relative links"

.github/workflows/cleanrepo-replace-redirects.yml

@@ -35,7 +35,7 @@
 
       # Create the PR for the work done by the "clean repo" tool
       - name: create-pull-request
-        uses: dotnet/actions-create-pull-request@v4
+        uses: peter-evans/create-pull-request@v7
         with:
           branch: cleanrepo-replace-redirects
           title: "Monthly chores: Replace redirect targets"

.github/workflows/dependabot-bot.yml

@@ -54,7 +54,7 @@
           dependabot-yml-path: ".github/dependabot.yml"
       - name: Create pull request
         if: github.event_name == 'workflow_dispatch' || github.repository_owner == 'dotnet'
-        uses: dotnet/actions-create-pull-request@v4
+        uses: peter-evans/create-pull-request@v7
         with:
           branch: create-dependabotconfig-pull-request/patch
           title: "Update dependabot.yml - automatically."

docs/core/compatibility/serialization/7.0/binaryformatter-apis-produce-errors.md

@@ -49,7 +49,7 @@ The best course of action is to migrate away from `BinaryFormatter` due to its s
 If you must suppress the errors, you can do so by following the guidelines in the [original obsoletion article](../5.0/binaryformatter-serialization-obsolete.md#recommended-action). You can also disable the error project-wide by setting a project property that converts the error back to a warning (to match the .NET 5/6 behavior).
 
 > [!WARNING]
-> Setting this property might change host behavior. See [\<EnableUnsafeBinaryFormatterSerialization> property](#enableunsafebinaryformatterserialization-property).
+> Setting this property might change host behavior. See [`<EnableUnsafeBinaryFormatterSerialization>` property](#enableunsafebinaryformatterserialization-property).
 
 ```csharp
 <PropertyGroup>
@@ -61,7 +61,7 @@ If you must suppress the errors, you can do so by following the guidelines in th
 > [!NOTE]
 > If your project compiles with "warnings as errors" enabled, compilation will still fail. (This matches the behavior that shipped in the .NET 5 and .NET 6 SDKs.) If that's the case, you'll still need to suppress the `SYSLIB0011` warning in source or in your project file's `<NoWarn>` element.
 
-### \<EnableUnsafeBinaryFormatterSerialization> property
+### `<EnableUnsafeBinaryFormatterSerialization>` property
 
 The `<EnableUnsafeBinaryFormatterSerialization` property was introduced in .NET 5. With .NET 7, the behavior of this switch has changed to control *both compilation and host* run-time behavior. The meaning of this switch differs based on the project type, as described in the following table.
 

docs/core/deploying/runtime-store.md

@@ -108,7 +108,7 @@ When the deployment is *trimmed* on publish, only the specific versions of the m
 
 ## Specifying target manifests in the project file
 
-An alternative to specifying target manifests with the [`dotnet publish`](../tools/dotnet-publish.md) command is to specify them in the project file as a semicolon-separated list of paths under a **\<TargetManifestFiles>** tag.
+An alternative to specifying target manifests with the [`dotnet publish`](../tools/dotnet-publish.md) command is to specify them in the project file as a semicolon-separated list of paths under a `<TargetManifestFiles>` tag.
 
 ```xml
 <PropertyGroup>
@@ -126,7 +126,7 @@ For .NET Core 2.0, the runtime package store feature is used implicitly by an AS
 
 The runtime package store is installed on the host when the .NET SDK is installed. Other installers may provide the runtime package store, including Zip/tarball installations of the .NET SDK, `apt-get`, Red Hat Yum, the .NET Core Windows Server Hosting bundle, and manual runtime package store installations.
 
-When deploying a [framework-dependent deployment](index.md#framework-dependent-deployment) app, make sure that the target environment has the .NET SDK installed. If the app is deployed to an environment that doesn't include ASP.NET Core, you can opt out of the implicit store by specifying  **\<PublishWithAspNetCoreTargetManifest>** set to `false` in the project file as in the following example:
+When deploying a [framework-dependent deployment](index.md#framework-dependent-deployment) app, make sure that the target environment has the .NET SDK installed. If the app is deployed to an environment that doesn't include ASP.NET Core, you can opt out of the implicit store by specifying  `<PublishWithAspNetCoreTargetManifest>` set to `false` in the project file as in the following example:
 
 ```xml
 <PropertyGroup>
@@ -135,7 +135,7 @@ When deploying a [framework-dependent deployment](index.md#framework-dependent-d
 ```
 
 > [!NOTE]
-> For [self-contained deployment](index.md#self-contained-deployment) apps, it's assumed that the target system doesn't necessarily contain the required manifest packages. Therefore, **\<PublishWithAspNetCoreTargetManifest>** cannot be set to `true` for an self-contained app.
+> For [self-contained deployment](index.md#self-contained-deployment) apps, it's assumed that the target system doesn't necessarily contain the required manifest packages. Therefore, `<PublishWithAspNetCoreTargetManifest>` cannot be set to `true` for an self-contained app.
 
 ## See also
 

docs/core/extensions/best-practices-for-developing-world-ready-apps.md

@@ -88,7 +88,7 @@ This section describes the best practices to follow when developing world-ready
 
 1. Specify the values for the `requestEncoding`, `responseEncoding`, `fileEncoding`, `culture`, and `uiCulture` attributes in the following three places in an ASP.NET application:
 
-    - In the globalization section of a _Web.config_ file. This file is external to the ASP.NET application. For more information, see [\<globalization> element](/previous-versions/dotnet/netframework-4.0/hy4kkhe0(v=vs.100)).
+    - In the globalization section of a _Web.config_ file. This file is external to the ASP.NET application. For more information, see [`<globalization>` element](/previous-versions/dotnet/netframework-4.0/hy4kkhe0(v=vs.100)).
     - In a page directive. Note that, when an application is in a page, the file has already been read. Therefore, it is too late to specify fileEncoding and requestEncoding. Only `uiCulture`, `culture`, and `responseEncoding` can be specified in a page directive.
     - Programmatically in application code. This setting can vary per request. As with a page directive, by the time the application's code is reached, it is too late to specify `fileEncoding` and `requestEncoding`. Only `uiCulture`, `culture`, and `responseEncoding` can be specified in the application code.
 

docs/core/testing/unit-testing-mstest-migration-from-v1-to-v3.md

@@ -3,7 +3,7 @@ title: MSTest migration to v3
 description: Learn about migrating from legacy MSTest (MSTest v1) to latest MSTest (MSTest v3).
 author: engyebrahim
 ms.author: enjieid
-ms.date: 11/06/2024
+ms.date: 11/28/2025
 ---
 
 # MSTest v3 migration guide
@@ -21,9 +21,9 @@ If your project relies on MSTest for unit testing and includes the above referen
 
 ### Why migrate to MSTest v3?
 
-Even if you’re satisfied with your current MSTest setup, upgrading to MSTest v3 unlocks substantial advantages that improve both the quality and future-readiness of your tests. Here’s why making the switch now can be a valuable step forward:
+Even if you're satisfied with your current MSTest setup, upgrading to MSTest v3 unlocks substantial advantages that improve both the quality and future-readiness of your tests. Here's why making the switch now can be a valuable step forward:
 
-- **Enhanced security**: MSTest v1 has known security vulnerabilities. With MSTest v3, we’ve implemented extensive security improvements to safeguard your testing environment.
+- **Enhanced security**: MSTest v1 has known security vulnerabilities. With MSTest v3, we've implemented extensive security improvements to safeguard your testing environment.
 - **Immediate Performance Boosts**: MSTest v3 significantly reduces test execution time and optimizes resource usage. This is particularly beneficial in CI/CD pipelines, where faster tests can shorten deployment cycles and cut infrastructure costs.
 
 - **Future-Proofing Your Tests**: MSTest v3 offers robust support for modern .NET versions, including .NET 8, and future iterations, along with cross-platform compatibility. This means your tests will be more adaptable and ready for upgrades, avoiding the technical debt of outdated testing frameworks.
@@ -36,7 +36,10 @@ Even if you’re satisfied with your current MSTest setup, upgrading to MSTest v
 
 - **Greater Flexibility and Extensibility**: MSTest v3 supports advanced testing scenarios, including dynamic data sources and in-assembly parallel execution. This flexibility enables more sophisticated testing approaches and speeds up test suites without complex configurations.
 
-By upgrading, you’re setting up your tests to be faster, more reliable, and adaptable to future .NET developments, positioning your project for long-term success and easier maintenance.
+By upgrading, you're setting up your tests to be faster, more reliable, and adaptable to future .NET developments, positioning your project for long-term success and easier maintenance.
+
+> [!TIP]
+> After migrating to MSTest v3, consider taking a further step and migrate to MSTest v4. For more information, see [Migrate from MSTest v3 to v4](./unit-testing-mstest-migration-v3-v4.md).
 
 ## Migration steps
 
@@ -54,7 +57,7 @@ In non-SDK style projects, these references are often added through Visual Studi
 4. Inside the **References** folder, **find and select** the MSTest DLL references, `Microsoft.VisualStudio.QualityTools.UnitTestFramework`
 5. **Right-click** the selected reference(s) and choose **Remove** from the context menu.
 
-    ![image](https://github.com/user-attachments/assets/7aff1afb-e26b-4450-bc2e-903a577e3df2)
+    ![Context menu of the assembly reference](https://github.com/user-attachments/assets/7aff1afb-e26b-4450-bc2e-903a577e3df2)
 
 6. **Save the project** to apply changes.
 
@@ -65,20 +68,20 @@ You can update your project to MSTest v3 in one of two ways:
 - **Update Packages**: If you have NuGet package references to the [MSTest.TestFramework](https://www.nuget.org/packages/MSTest.TestFramework) and the [MSTest.TestAdapter](https://www.nuget.org/packages/MSTest.TestAdapter/), update them using the NuGet Package Manager in Visual Studio or by running the following command in the NuGet Package Manager Console:
 
     ```shell
-    Update-Package MSTest.TestFramework -Version 3.6.2
-    Update-Package MSTest.TestAdapter -Version 3.6.2
+    Update-Package MSTest.TestFramework -Version 3.11.1
+    Update-Package MSTest.TestAdapter -Version 3.11.1
     ```
 
 - **Or Install MSTest Package**: Install the latest [MSTest](https://www.nuget.org/packages/MSTest) package using the NuGet Package Manager in Visual Studio or by running the following command in the NuGet Package Manager Console:
 
     ```shell
-    Install-Package MSTest -Version 3.6.2
+    Install-Package MSTest -Version 3.11.1
     ```
 
 - **Or update the project file directly** (for SDK-style projects): Update your `.csproj` file to specify the MSTest SDK version.
 
     ```xml
-    <Project Sdk="MSTest.Sdk/3.6.2">
+    <Project Sdk="MSTest.Sdk/3.11.1">
       <PropertyGroup>
         <TargetFramework>net8.0</TargetFramework>
       </PropertyGroup>
@@ -140,7 +143,7 @@ The DataRowAttribute constructors in MSTest v3 have been simplified to enforce t
 public void MyTestMethod(int number, string text) { ... }
 ```
 
-In cases where types don’t match exactly, MSTest v3 will now raise an error rather than attempting a conversion.
+In cases where types don't match exactly, MSTest v3 will now raise an error rather than attempting a conversion.
 
 ### Timeout settings
 

docs/core/tools/dependencies.md

@@ -9,7 +9,7 @@ ms.date: 01/28/2021
 
 This article explains how to add and remove package dependencies by editing the project file or by using the CLI.
 
-## The \<PackageReference> element
+## The `<PackageReference>` element
 
 The `<PackageReference>` project file element has the following structure:
 

docs/core/tools/dotnet-test.md

@@ -490,7 +490,7 @@ With Microsoft Testing Platform, `dotnet test` operates faster than with VSTest.
 
 - **`--max-parallel-test-modules <NUMBER>`**
 
-  Specifies the maximum number of test modules that can run in parallel.
+  Specifies the maximum number of test modules that can run in parallel. The default is <xref:System.Environment.ProcessorCount?displayProperty=nameWithType>.
 
 - [!INCLUDE [arch](../../../includes/cli-arch.md)]
 

docs/core/tutorials/library-with-visual-studio-code.md

@@ -33,7 +33,7 @@ Start by creating a .NET class library project named "StringLibrary" and an asso
 
 1. Name the project **StringLibrary** and select **Create Project**.
 
-1. Press Enter at the prompt **Project will be created in \<path>**.
+1. Press <kbd>Enter</kbd> at the prompt **Project will be created in \<path>**.
 
 1. Check to make sure that the library targets .NET 9. In **Explorer**, open *StringLibrary/StringLibrary.csproj*.