Merge pull request #10713 from MicrosoftDocs/main638802758234009520sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/code-quality/code-metrics-values.md

@@ -1,6 +1,6 @@
 ---
 title: How code metrics help identify risks
-ms.date: 11/29/2023
+ms.date: 04/14/2025
 description: Learn about cyclomatic complexity, class coupling, and other Visual Studio code metrics. See how metrics can track development progress and identify risks.
 ms.topic: conceptual
 f1_keywords:

docs/code-quality/how-to-generate-code-metrics-data.md

@@ -1,6 +1,6 @@
 ---
 title: Generate code metrics from the IDE or command line
-ms.date: 11/02/2018
+ms.date: 04/14/2025
 description: Learn how to generate code metrics data in Visual Studio. See how to use Solution Explorer, a rule set file, the command line, or a menu command.
 ms.topic: how-to
 helpviewer_keywords:

docs/code-quality/install-net-analyzers.md

@@ -1,6 +1,6 @@
 ---
 title: Enable or install first-party .NET analyzers
-ms.date: 09/14/2023
+ms.date: 04/14/2025
 description: Enable first-party .NET analyzers by using the .NET SDK in Visual Studio or install a first-party analyzer as a NuGet package.
 ms.topic: how-to
 helpviewer_keywords:
@@ -13,13 +13,13 @@ ms.subservice: code-analysis
 
 # Enable or install first-party .NET analyzers
 
-.NET compiler platform (Roslyn) analyzers inspect your C# or Visual Basic code for code quality and code style issues. The first-party .NET analyzers are **target-platform agnostic**. That is, your project doesn't need to target a specific .NET platform. The analyzers work for projects that target `net5.0` and earlier .NET versions, such as `netcoreapp`, `netstandard`, and `net472`.
+.NET compiler platform (Roslyn) analyzers inspect your C# or Visual Basic code for code quality and code style issues. The first-party .NET analyzers are **target-platform agnostic**. That is, your project doesn't need to target a specific .NET platform. The analyzers work for projects that target `net5.0`, later versions, as well as earlier .NET versions, such as `netcoreapp`, `netstandard`, and `net472`.
 
 You can enable or install the first-party .NET analyzers in one of the following ways:
 
 - **Enable from the .NET SDK:** Starting in Visual Studio 2019 16.8 and .NET 5.0, these analyzers are [included with the .NET SDK](/dotnet/fundamentals/code-analysis/overview), which is included with Visual Studio. Analysis is enabled, by default, for projects that target .NET 5.0 or later. You can enable code analysis on projects that target earlier .NET versions by setting the MSBUILD [EnableNETAnalyzers](/dotnet/core/project-sdk/msbuild-props#enablenetanalyzers) property to `true`. You can also disable code analysis for your project by setting `EnableNETAnalyzers` to `false`.
 
-- **Install as a NuGet package:** If you don't want to move to the .NET 5+ SDK or if you prefer a NuGet package-based model, the analyzers are also available in the `Microsoft.CodeAnalysis.NetAnalyzers` [NuGet package](https://www.nuget.org/packages/Microsoft.CodeAnalysis.NetAnalyzers) on Visual Studio 2019. You might prefer a package-based model for on-demand version updates. If you're on Visual Studio 2017, install the latest `2.9.x` version of the `Microsoft.CodeAnalysis.FxCopAnalyzers` [NuGet package](https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/) instead.
+- **Install as a NuGet package:** If you don't want to move to the .NET 5+ SDK or if you prefer a NuGet package-based model, the analyzers are also available in the `Microsoft.CodeAnalysis.NetAnalyzers` [NuGet package](https://www.nuget.org/packages/Microsoft.CodeAnalysis.NetAnalyzers) on Visual Studio 2019 and Visual Studio 2022. You might prefer a package-based model for on-demand version updates. If you're on Visual Studio 2017, install the latest `2.9.x` version of the `Microsoft.CodeAnalysis.FxCopAnalyzers` [NuGet package](https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/) instead.
 
 > [!NOTE]
 > It is recommended that you enable the analyzers from the .NET SDK instead of installing the `Microsoft.CodeAnalysis.NetAnalyzers` [NuGet package](https://www.nuget.org/packages/Microsoft.CodeAnalysis.NetAnalyzers), when possible. Enabling the analyzers from the .NET SDK ensures that you automatically get the analyzer bug fixes and new analyzers as soon as you update the SDK. In the NuGet model, you need to update the NuGet package each time you want the latest bug fixes. The NuGet package is updated more frequently.

docs/msbuild/errors/msb3103.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3103: Invalid Resx file"
-description: "This error occurs when there's an issue with a .resx resource file."
-ms.date: "1/27/2025"
+title: MSB3103 diagnostic code
+description: Learn about the possible causes of the MSB3103 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3103
@@ -16,52 +16,52 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSB3103: Invalid Resx file
+# MSB3103
 
-This error occurs when there/s an issue with a `.resx` resource file. When you see this error, another error is displayed with more details. Look to the other error for more information.
+This article describes the MSB3103 error code.
 
 ## Message text
 
-`MSB3103: Invalid Resx file`
+`Invalid Resx file`
 
-## Remarks
+## Description
 
-The error MSB3103 occurs when MSBuild encounters an invalid `.resx` file during the build process. This error indicates that the `.resx` file can't be properly read or processed, often due to incorrect file paths or references. 
+This error occurs when there's an issue with a `.resx` resource file. This error indicates that the `.resx` file can't be properly read or processed, often due to incorrect file paths or references. 
 
-## Common Causes
+### Common causes
 
-This error can occur in the following scenarios:
+The following causes can result in this error:
 
-1. **Missing or Inaccessible Resources**: The `.resx` file references external resources (for example, images or files) that aren't present in the expected location or are inaccessible.
-    - Example: A file path specified in the `.resx` is incorrect or points to a missing file.
-2. **Incorrect type reference**: The `.resx` file referenced a type that couldn't be found.
-    - Example: A typo in a type reference in a ResXFile reference, or a type that was not available for some reason.
-3. **Corrupted files**: The `.resx` file or one of its dependencies was corrupted.
+| Cause | Description | Example |
+| --- | --- | --- |
+| **Missing or inaccessible resources** | The `.resx` file references external resources (for example, images or files) that aren't present in the expected location or are inaccessible. | A file path specified in the `.resx` file is incorrect or points to a missing file. |
+| **Incorrect type reference** | The `.resx` file referenced a type that can't be found. | A typo in a type reference in a ResXFile reference, or a type that isn't available for some reason. |
+| **Corrupted files** | The `.resx` file or one of its dependencies is corrupted. | The `.resx` file contains unreadable characters and the build isn't able to process the file. |
 
-## Real-World Scenarios
+### Real-world scenarios
 
-1. **Migrating projects**: When you're upgrading a legacy project from .NET Framework to .NET Core or .NET 6+, existing `.resx` files may contain elements or attributes that are incompatible with the newer frameworks.
-2. **Manual edits to `.resx` files**: Someone manually editing `.resx` files might inadvertently introduce syntax errors or invalid data.
-3. **Broken resource links**: Referencing external files (for example, images or icons) in `.resx` files without ensuring these files are included in the project or accessible during the build.
-4. **Corrupted `.resx` files**: Files can become corrupted due to version control conflicts or file encoding changes.
+Here are some real-world scenarios that can lead to this error:
 
-### Resolution
+- **Project migration**: Upgrading a legacy project from .NET Framework to .NET Core or .NET 6+ where existing `.resx` files contain elements or attributes that aren't compatible with the newer frameworks.
 
-1. **Check Resource Entries**:
-    - If external resources are referenced, verify their paths and existence.
+- **Manual edits to .resx files**: Manual edits to `.resx` files that inadvertently introduce syntax errors or invalid data.
 
-2. **Use the ResX Resource Manager**:
-    - Consider using tools like [ResX Resource Manager](https://github.com/dotnet/ResXResourceManager) to validate and manage `.resx` files.
+- **Broken resource links**: References to external files (for example, images or icons) in `.resx` files where the files aren't included in the project or accessible during the build.
 
-3. **Update for Framework Compatibility**:
-    - Review changes in resource handling for the target framework.
-    - Update `.resx` files to align with the requirements of the new framework.
+- **Corrupted .resx files**: Files are corrupted due to version control conflicts or file encoding changes.
+ 
+## Resolution
 
-4. **Revert to a Known Good State**:
-    - If the `.resx` file has become corrupted, revert to a previous version from source control.
+- **Check resource entries**: If external resources are referenced, verify their paths and existence.
 
+- **Use the ResX Resource Manager**: Consider using tools like [ResX Resource Manager](https://github.com/dotnet/ResXResourceManager) to validate and manage `.resx` files.
 
-## Related Content
+- **Update for framework compatibility**: Review changes in resource handling for the target framework. Update `.resx` files to align with the requirements of the new framework.
 
-- [MSBuild Documentation](../msbuild.md)
-- [ResX Resource Manager](https://github.com/dotnet/ResXResourceManager)
+- **Revert to a known good state**: If the `.resx` file is corrupted, revert to a previous version from source control.
+
+For more information, see [MSBuild Documentation](../msbuild.md) and [ResX Resource Manager](https://github.com/dotnet/ResXResourceManager).
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb3190.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3190: ClickOnce does not support the request execution level 'level'"
-description: "This error occurs when an *app.manifest* included in the project does not have UAC Execution level set to `asInvoker` (which ClickOnce requires)."
-ms.date: "07/22/2021"
+title: MSB3190 diagnostic code
+description: Learn about the possible causes of the MSB3190 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3190
@@ -16,11 +16,21 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSB3190: ClickOnce does not support the request execution level 'level'
+# MSB3190
 
-This error occurs when an *app.manifest* included in the project does not have UAC Execution level set to `asInvoker` (which ClickOnce requires).
+This article describes the MSB3190 error code.
 
-To resolve this error, make sure you have the following in *app.manifest* under the `trustInfo` settings:
+## Message text
+
+`ClickOnce does not support the request execution level 'level'`
+
+## Description
+
+This error occurs when an *app.manifest* file included in the project doesn't have UAC Execution level set to `asInvoker` (which ClickOnce requires).
+
+## Resolution
+
+To resolve this error, make sure you have the following definition in the *app.manifest* file under the `trustInfo` settings:
 
 ```xml
   <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2"> 
@@ -33,4 +43,8 @@ To resolve this error, make sure you have the following in *app.manifest* under
 <requestedExecutionLevel level="asInvoker" uiAccess="false" />
 ```
 
-See [requestedExecutionLevel](../../deployment/trustinfo-element-clickonce-application.md#requestedexecutionlevel).
+For more information, see [requestedExecutionLevel](../../deployment/trustinfo-element-clickonce-application.md#requestedexecutionlevel).
+
+## Applies to
+
+All versions of MSBuild

docs/msbuild/errors/msb3191.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3191: Unable to create directory 'name'."
-description: "This error occurs when MSBuild could not create a directory."
-ms.date: "08/15/2022"
+title: MSB3191 diagnostic code
+description: Learn about the possible causes of the MSB3191 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3191
@@ -18,10 +18,20 @@ ms.subservice: msbuild
 ---
 # MSB3191
 
+This article describes the MSB3191 error code.
+
+## Message text
+
+`MSB3191: Unable to create directory 'name'.`
+
+## Description
+
 This error occurs when MSBuild attempts to create a directory, but the operating system returns an error.
 
-```output
-MSB3191: Unable to create directory 'name'.
-```
+## Resolution
+
+The standard output message text is followed by additional information from the operating system. Look to the additional information provided to determine the cause of the problem.
+
+## Applies to
 
-When this message is emitted, the error text from the operating system is also given. Look to the additional information to determine the cause of the problem.
+All versions of MSBuild

docs/msbuild/errors/msb3202.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3202: The project file 'filename' was not found."
-description: "This error occurs when MSBuild can't find a project file with the specified name at the expected location."
-ms.date: 1/21/2025
+title: MSB3202 diagnostic code
+description: Learn about the possible causes of the MSB3202 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3202
@@ -18,40 +18,34 @@ ms.subservice: msbuild
 ---
 # MSB3202
 
-This error occurs when MSBuild can't find a project file with the specified name at the expected location.
+This article describes the MSB3202 error code.
 
-The full message is something like the following text:
+## Message text
 
-```output
-MSB3202: The project file 'filename' was not found.
-```
+`MSB3202: The project file 'filename' was not found.`
 
-## Remarks
+## Description
 
 The MSB3202 error occurs when MSBuild is unable to locate the specified project file. This error is generated when a build is invoked with an incorrect or missing project file path, or incorrect or missing dependent project file.
 
-## Common causes
+### Real-world scenarios
 
-Here are some real-world scenarios that can lead to this error, especially in modern development and CI/CD environments:
+Here are some real-world scenarios that can produce this error, especially in modern development and CI/CD environments:
 
-1. **Incorrect file path in command line or build script**
-   - When invoking MSBuild, the specified project file path doesn't exist or is mistyped. Check the path, especially for syntax issues such as quotes around paths with spaces.
+- **Incorrect file path in command line or build script**: When you invoke MSBuild, the specified project file path doesn't exist or is mistyped.
 
-2. **Project file renamed or deleted**
-   - A project file was renamed or removed from the repository, but the build logic or one of the build inputs was not updated to reflect this change.
+- **Project file renamed or deleted**: A project file was renamed or removed from the repository, but the build logic or one of the build inputs isn't updated to reflect the change.
 
-3. **Repository checkout issues**
-   - During a CI/CD pipeline execution, the source code repository might not be fully checked out, or the necessary project file is excluded due to `.gitignore` rules or shallow cloning.
+- **Repository checkout issues**: During a CI/CD pipeline execution, the source code repository might not be fully checked out, or the necessary project file is excluded due to `.gitignore` rules or shallow cloning.
 
 ## Resolution
 
-1. Verify that the project file exists at the specified location.
-   - Use an absolute path to the project file to avoid ambiguity.
-   - Example:
+- Verify the project file exists at the specified location. Avoid ambiguity by using an absolute path to the project file, such as `msbuild C:\Projects\MySolution\MyProject.csproj`.
 
-     `msbuild C:\Projects\MySolution\MyProject.csproj`
+- Check for typos in the `ProjectReference` item in the project file. Confirm the path has no syntax issues like missing quotes for paths that include spaces.
 
-2. Check for typos in the ProjectReference item in the project file.
+- Ensure your version control system includes all necessary project files and the repository checkout is complete.
 
-3. Ensure your version control system includes all necessary project files and that the repository checkout is complete.
+## Applies to
 
+All versions of MSBuild

docs/msbuild/errors/msb3231.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3231: Unable to remove directory 'name'."
-description: "This error occurs when MSBuild tries to delete a directory, but the operating system returns an error."
-ms.date: "08/15/2022"
+title: MSB3231 diagnostic code
+description: Learn about the possible causes of the MSB3231 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3231
@@ -18,12 +18,20 @@ ms.subservice: msbuild
 ---
 # MSB3231
 
+This article describes the MSB3231 error code.
+
+## Message text
+
+`MSB3231: Unable to remove directory 'name'.`
+
+## Description
+
 This error occurs when MSBuild tries to delete a directory, but the operating system returns an error.
 
-The message resembles the following, but this text is followed by additional information from the operating system:
+## Resolution
+
+The standard output message text is followed by additional information from the operating system. Look to the additional information provided to determine the cause of the problem.
 
-```output
-MSB3231: Unable to remove directory 'name'.
-```
+## Applies to
 
-Look to the additional information provided by the operating system to determine the cause of the problem.
+All versions of MSBuild

docs/msbuild/errors/msb3243.md

@@ -1,7 +1,7 @@
 ---
-title: "MSB3243: No way to resolve conflict between 'first assembly' and 'second assembly'. Choosing 'first assembly' arbitrarily."
-description: "This diagnostic code is emitted when MSBuild finds two conflicting assemblies for a given reference, with no way to resolve the conflict."
-ms.date: "08/15/2022"
+title: MSB3243 diagnostic code
+description: Learn about the possible causes of the MSB3243 build error and get troubleshooting tips.
+ms.date: 04/15/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3243
@@ -18,14 +18,22 @@ ms.subservice: msbuild
 ---
 # MSB3243
 
-This diagnostic code is emitted when MSBuild finds two conflicting assemblies for a given reference, with no way to resolve the conflict. In such cases, MSBuild chooses one of the assemblies arbitrarily and continues processing the build.
+This article describes the MSB3243 error code.
+
+## Message text
 
-The message text resembles the following text:
+`MSB3243: No way to resolve conflict between 'first assembly' and 'second assembly'. Choosing 'first assembly' arbitrarily.`
 
-```output
-MSB3243: No way to resolve conflict between 'first assembly' and 'second assembly'. Choosing 'first assembly' arbitrarily.
-```
+## Description
+
+This diagnostic code is emitted when MSBuild finds two conflicting assemblies for a given reference, with no way to resolve the conflict. In such cases, MSBuild chooses one of the assemblies arbitrarily and continues processing the build.
 
-A diagnostic build log will have more information about how the two conflicting assemblies were found which may help restructure your build to avoid the warning.
+## Resolution
+
+A diagnostic build log has more information about how the two conflicting assemblies were found. The log information might help you to restructure your build to avoid the warning.
 
 For a guide on resolving errors with assembly references, see [Troubleshoot assembly references](../troubleshoot-assembly-references.md).
+
+## Applies to
+
+All versions of MSBuild