Merge pull request #10596 from MicrosoftDocs/main638736842380936605sync_temp

learn-build-service-prod[bot] · web-flow · commit 62c988498da7 · 2025-01-28T18:04:10.000Z
For protected branch, push strategy should use PR and merge to target branch method to work around git push error
diff --git a/docs/debugger/adapt-to-removal-of-windows-arm32-dotnet-debugging.md b/docs/debugger/adapt-to-removal-of-windows-arm32-dotnet-debugging.md
@@ -36,10 +36,14 @@ Visual Studio 17.12 can be used from the Long-Term Servicing Channel (LTSC). For
 
 ## Option 3: Start without debugging 
 
-If you have a project that you still want to run but doesn't require debugging, use **Debug->Start without debugging** to run the project. Since the debugger isn't available, you would need to diagnose any problems by using logging. 
+If you have a project that you still want to run but doesn't require debugging, you could launch it without debugging. Since the debugger isn't available, you would need to diagnose any problems by using logging.
+
+If your project is a Universal Windows Platform (UWP) project, and the target device is running an Arm32 version of Windows, then you need to manually deploy the project to run it. To do so, build your project to an .appx file, copy the appx to your device, use the WinAppDeployCmd.exe tool to install the .appx, and then start the application from the start menu. For more information, see [Install apps with the WinAppDeployCmd.exe tool](/windows/uwp/packaging/install-universal-windows-apps-with-the-winappdeploycmd-tool).
+
+For other types of projects, you can still use **Debug > Start without debugging** to run the project. 
 
 > [!NOTE]
-> This option is not recommended since .NET support for Windows on Arm32 has ended.
+> This option isn't recommended since .NET support for Windows on Arm32 has ended.
 
 
 ## Option 4: Target Linux 
diff --git a/docs/get-started/csharp/index.yml b/docs/get-started/csharp/index.yml
@@ -13,7 +13,7 @@ metadata:
   ms.author: ghogen  
   manager: mijacobs
   
-  ms.subservice: vs-acquisition  
+  ms.subservice: general-ide  
   dev_langs:
     - CSharp
 
diff --git a/docs/get-started/visual-basic/index.yml b/docs/get-started/visual-basic/index.yml
@@ -13,7 +13,7 @@ metadata:
   author: ghogen
   manager: mijacobs
   
-  ms.subservice: vs-acquisition
+  ms.subservice: general-ide
   dev_langs:
     - VB
 
diff --git a/docs/ide/compare-with.md b/docs/ide/compare-with.md
@@ -2,7 +2,7 @@
 title: Compare files in Visual Studio
 titleSuffix: ""
 description: Compare or diff two files in Visual Studio to see where changes are by viewing the files side-by-side in a split screen, and to see line-by-line what is different.
-ms.date: 03/12/2024
+ms.date: 01/27/2025
 ms.topic: how-to
 author: ghogen
 ms.author: ghogen
@@ -34,7 +34,7 @@ From the [Developer Command Prompt](./reference/command-prompt-powershell.md), u
 devenv /Diff SourceFile TargetFile [SourceDisplayName [TargetDisplayName]]
 ```
 
-Visual Studio opens with the two files shown side-by-side, but a project is not opened. The `TargetFile` is considered the newer version, and is editable.
+Visual Studio opens with the two files shown side-by-side, but a project is not opened. The `TargetFile` is considered the newer version, and is editable. In the target file, you can make changes in the usual ways such as typing, pasting code from the clipboard, and so on.
 
 ## Understand differences
 
diff --git a/docs/ide/finding-and-replacing-text.md b/docs/ide/finding-and-replacing-text.md
@@ -102,7 +102,7 @@ Open the **Find and Replace** dialog box by pressing **Ctrl**+**Shift**+**F**, o
 
 :::moniker-end
 
-To expose the **Replace** text box, use the down arrow to the left of the **Find** text.
+To expose the **Replace** text box, use the down arrow to the left of the **Find** text, or choose the tab **Replace in Files**. When you switch to replace mode, an additional text field appears for the replacement text, and a checkbox appears that provides the option to preserve case when replacing text.
 
 Set the scope of your search and replace operation to:
 
@@ -117,6 +117,8 @@ The **Find and Replace** tool does not search directories with the `Hidden` or `
 
 To cancel a Find or Replace operation, press **Ctrl**+**Break**.
 
+For more information, see [Find in files](../ide/find-in-files.md) and [Replace in files](../ide/replace-in-files.md), and for more about using regular expressions, see [Use Regular Expressions](../ide/using-regular-expressions-in-visual-studio.md).
+
 ### Find Results
 
 When you choose **Find All**, a **Find Results** window opens and lists the matches for your search. Selecting a result in the list displays the associated file and highlights the match. If the file is not already open for editing, it is opened in a preview tab in the right side of the tab well. You can use the **Find** control to search through the **Find Results** list.
diff --git a/docs/msbuild/errors/msb3103.md b/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: "06/18/2021"
+ms.date: "1/27/2025"
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3103
@@ -18,4 +18,50 @@ ms.subservice: msbuild
 ---
 # MSB3103: Invalid Resx file
 
-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 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.
+
+## Message text
+
+`MSB3103: Invalid Resx file`
+
+## Remarks
+
+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. 
+
+## Common Causes
+
+This error can occur in the following scenarios:
+
+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.
+
+## 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.
+
+### Resolution
+
+1. **Check Resource Entries**:
+    - If external resources are referenced, verify their paths and existence.
+
+2. **Use the ResX Resource Manager**:
+    - Consider using tools like [ResX Resource Manager](https://github.com/dotnet/ResXResourceManager) to validate and manage `.resx` files.
+
+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.
+
+4. **Revert to a Known Good State**:
+    - If the `.resx` file has become corrupted, revert to a previous version from source control.
+
+
+## Related Content
+
+- [MSBuild Documentation](../msbuild.md)
+- [ResX Resource Manager](https://github.com/dotnet/ResXResourceManager)
diff --git a/docs/msbuild/errors/msb3202.md b/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: "08/15/2022"
+ms.date: 1/21/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3202
@@ -26,4 +26,32 @@ The full message is something like the following text:
 MSB3202: The project file 'filename' was not found.
 ```
 
-Make sure the current directory is correct and that the specified project file exists and that the filename is spelled correctly.
+## Remarks
+
+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
+
+Here are some real-world scenarios that can lead to 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.
+
+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.
+
+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.
+
+## Resolution
+
+1. Verify that the project file exists at the specified location.
+   - Use an absolute path to the project file to avoid ambiguity.
+   - Example:
+
+     `msbuild C:\Projects\MySolution\MyProject.csproj`
+
+2. Check for typos in the ProjectReference item in the project file.
+
+3. Ensure your version control system includes all necessary project files and that the repository checkout is complete.
+
diff --git a/docs/msbuild/errors/msb3245.md b/docs/msbuild/errors/msb3245.md
@@ -1,7 +1,7 @@
 ---
 title: "MSB3245: Could not resolve this reference. 'assembly' If this reference is required by your code, you may get compilation errors."
 description: "This diagnostic code is emitted when MSBuild can't find an assembly referenced in your project."
-ms.date: "08/15/2022"
+ms.date: 1/21/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3245
@@ -22,10 +22,12 @@ This diagnostic code is emitted when MSBuild can't resolve an assembly reference
 
 The full message resembles the following text:
 
-```output
-MSB3245: Could not resolve this reference. 'assembly' If this reference is required by your code, you may get compilation errors.
-```
+`MSB3245: Could not resolve this reference. 'assembly' If this reference is required by your code, you may get compilation errors.`
 
 This error might occur if the item is a directory, not a file, or it could occur if the assembly resolver for that reference returns an error. It could be any error that prevents resolution of the reference, such as a missing assembly, misspelled name, version mismatch, mismatched processor architecture, or failed `ProjectReference`.
 
-For a guide on resolving errors with assembly references, see [Troubleshoot assembly references](../troubleshoot-assembly-references.md).
+For a guide on resolving errors with assembly references, see [Troubleshoot assembly references](../troubleshoot-assembly-references.md).
+
+### Related content
+
+- [MSBuild ResolveAssemblyReference Task Documentation](../resolveassemblyreference-task.md)
diff --git a/docs/msbuild/errors/msb3248.md b/docs/msbuild/errors/msb3248.md
@@ -1,7 +1,7 @@
 ---
 title: "MSB3248 diagnostic code"
 description: "Parameter 'value' has invalid value 'value'."
-ms.date: 12/06/2024
+ms.date: 1/21/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3248
@@ -27,13 +27,32 @@ This article describes the MSB3248 error code.
 ## Message text
 
 ```output
-MSB3248: Parameter 'value' has invalid value 'value'.
+MSB3248: Parameter 'parameter name' has invalid value 'value'.
 ```
 
 <!-- :::editable-content name="postOutputDescription"::: -->
-<!--
-{StrBegin="MSB3248: "}
--->
+## Remarks
+
+The error code MSB3248 occurs in the `ResolveAssemblyReference` task in MSBuild when there's an issue with the parameters specified for resolving assembly references. The `ResolveAssemblyReference` task is responsible for resolving assembly references in a project. You don't normally invoke this task directly; it's called during the .NET build process.
+
+### Common causes
+
+The most likely cause is an MSBuild property setting that creates an issue with the assembly resolution process. See [Common MSBuild properties](../common-msbuild-project-properties.md).
+
+## Resolution
+
+Look at what specific parameter triggers the error and its value and review how it's set or modified in your project files or imported files.
+
+Enable detailed logging for your MSBuild process by using the `/v:diag` verbosity flag:
+
+```bash
+msbuild MyProject.proj /v:diag
+```
+
+This option provides a detailed log output, which should be helpful to determine which assembly reference is triggering the issue. Then, check the values of the properties that are related to that assembly, and the project that references it.
+
+You can also create a binary log by using the `-bl` command-line option, and use MSBuild [structured log viewer](https://msbuildlog.com/) to more easily view the log output. For more information, see [Troubleshoot assembly references](../troubleshoot-assembly-references.md).
+
 <!-- :::editable-content-end::: -->
 <!-- :::ErrorDefinitionDescription-end::: -->
 
diff --git a/docs/msbuild/errors/msb3249.md b/docs/msbuild/errors/msb3249.md
@@ -1,7 +1,7 @@
 ---
 title: "MSB3249 diagnostic code"
 description: "Application Configuration file 'value' is invalid."
-ms.date: 12/06/2024
+ms.date: 1/21/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3249
@@ -31,12 +31,41 @@ MSB3249: Application Configuration file 'value' is invalid.
 ```
 
 <!-- :::editable-content name="postOutputDescription"::: -->
-<!--
-{StrBegin="MSB3249: "}
--->
+
+### Remarks
+
+The error MSB3249 is raised by the `ResolveAssemblyReference` task in MSBuild when an invalid or malformed application configuration file (for example, `app.config`) is detected during the build process. This usually occurs when the configuration file contains syntax errors, invalid XML, or unexpected values that prevent MSBuild from properly resolving assembly references. See [ResolveAssemblyReference task](../resolveassemblyreference-task.md).
+
+### Possible causes
+
+1. **Malformed or invalid XML**: The `app.config` file contains syntax errors or is not well-formed XML.
+2. **Missing or incorrect `<runtime>` section**: The `app.config` file is missing the `<runtime>` element or contains invalid data in this section. See [`<runtime>` element](/dotnet/framework/configure-apps/file-schema/runtime/runtime-element).
+3. **Unrecognized configuration settings**: The file includes settings that are not supported or are incorrectly specified.
+4. **File not accessible**: The `app.config` file is missing, locked, or inaccessible due to file permissions.
+
+### Resolution
+
+1. **Validate the `app.config` file**:
+   - Open the file in an XML editor or IDE that supports XML validation.
+   - Correct any syntax errors or invalid XML structure.
+
+2. **Check for unsupported or invalid settings**:
+   - Review the file for any unrecognized configuration keys or invalid values.
+   - Refer to the [Configuring apps by using configuration files](/dotnet/framework/configure-apps/) for supported settings.
+
+3. **Ensure file accessibility**:
+   - Confirm that the `app.config` file exists in the expected location.
+   - Ensure the build process has the necessary permissions to read the file.
+
+The `ResolveAssemblyReference` task is responsible for resolving references to assemblies during the build process. An invalid `app.config` file can prevent this task from completing successfully. For more information on the `ResolveAssemblyReference` task, see [MSBuild ResolveAssemblyReference Task](../resolveassemblyreference-task.md).
+
 <!-- :::editable-content-end::: -->
 <!-- :::ErrorDefinitionDescription-end::: -->
 
+## Related content
+
+[ResolveAssemblyReference task](../resolveassemblyreference-task.md)
+
 ## Applies to
 
 All versions of MSBuild
diff --git a/docs/msbuild/errors/msb4066.md b/docs/msbuild/errors/msb4066.md
@@ -1,7 +1,7 @@
 ---
 title: "MSB4066 diagnostic code"
 description: "The attribute 'value' in element 'value' is unrecognized."
-ms.date: 12/06/2024
+ms.date: 1/21/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB4066
@@ -31,9 +31,25 @@ MSB4066: The attribute 'value' in element 'value' is unrecognized.
 ```
 
 <!-- :::editable-content name="postOutputDescription"::: -->
-<!--
-{StrBegin="MSB4066: "}
--->
+
+## Remarks
+
+This error occurs when MSBuild encounters an XML attribute in a project file or target file that it doesn't recognize. MSBuild validates the attributes of elements in project files to ensure they adhere to the correct MSBuild syntax and supported attributes for each element.
+
+## Possible causes
+
+The error is typically caused by one of the following:
+
+- A typo in an attribute name within an MSBuild project file (for example, `.csproj`, `.vbproj`, or `.proj`).
+- Use of an unsupported or obsolete attribute in a project file.
+- An attribute was added to the project file but isn't recognized by your version of MSBuild.
+
+## Resolution
+
+1. **Check for typos**: Verify that the attribute name is spelled correctly and matches the expected schema.
+2. **Remove unsupported attributes**: Cross-reference the MSBuild documentation to ensure that the attribute is valid for the specific element. See [MSBuild project file schema reference](../msbuild-project-file-schema-reference.md).
+3. **Update MSBuild version**: If the attribute is new and not recognized, ensure you're using a version of MSBuild that supports it.
+
 <!-- :::editable-content-end::: -->
 <!-- :::ErrorDefinitionDescription-end::: -->
 
diff --git a/docs/msbuild/errors/msb4186.md b/docs/msbuild/errors/msb4186.md
@@ -1,7 +1,7 @@
 ---
 title: "MSB4186 diagnostic code"
 description: "Invalid static method invocation syntax: 'value'. 'value' Static method invocation should be of the form: $([FullTypeName]::Method()), e.g. $([System.IO.Path]::Combine(`a`, `b`)). Check that all parameters are defined, are of the correct type, and are specified in the right order."
-ms.date: 12/06/2024
+ms.date: 1/21/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB4186
@@ -36,6 +36,21 @@ MSB4186: Invalid static method invocation syntax: 'value'. 'value' Static method
       UE: This message is shown when the user attempts to call a static method on a type, but has used the incorrect syntax
       LOCALIZATION: "{0}" is the function expression which is in error. "{1}" is a message from an FX exception that describes why the expression is bad.
 -->
+
+## Remarks
+
+This error occurs when MSBuild encounters a function invocation that uses an invalid syntax for calling a static method. In MSBuild, static methods must be invoked using the correct syntax: `$([FullTypeName]::Method(Parameters))`.
+
+### Resolution
+
+To resolve this error, ensure that the static method is invoked using the proper syntax, including the closing `]` and the `::`:
+
+```xml
+<PropertyGroup>
+    <MyProperty>$([ClassName]::MethodName('a', 'b'))</MyProperty>
+</PropertyGroup>
+```
+
 <!-- :::editable-content-end::: -->
 <!-- :::ErrorDefinitionDescription-end::: -->
 
diff --git a/docs/msbuild/errors/msb4211.md b/docs/msbuild/errors/msb4211.md
diff --git a/docs/msbuild/errors/msb4248.md b/docs/msbuild/errors/msb4248.md
diff --git a/docs/msbuild/xmlpoke-task.md b/docs/msbuild/xmlpoke-task.md
