Merge pull request #11070 from MicrosoftDocs/main638947839091932536sync_temp

Repo sync for protected branch

Author: v-dirichards

docs/designers/disable-dpi-awareness.md

@@ -8,6 +8,7 @@ manager: mijacobs
 ms.subservice: ui-designers
 ms.topic: how-to
 ms.custom: engagement-fy23
+monikerRange: "<=vs-2022"
 ---
 # Fix HDPI/scaling issues with Windows Forms Designer in Visual Studio 
 

docs/designers/scaling-percentage-display-setting-message.md

@@ -7,6 +7,7 @@ author: ghogen
 ms.author: ghogen
 manager: mijacobs
 ms.subservice: ui-designers
+monikerRange: "<=vs-2022"
 ---
 # Scaling on your main display is set to X%
 

docs/ide/finding-references.md

@@ -1,7 +1,7 @@
 ---
 title: Finding References in Your Code
 description: Use the Find All References command in Visual Studio to find references to particular code elements in your code. Search by reference type.
-ms.date: 04/05/2025
+ms.date: 9/29/2025
 ms.topic: conceptual
 helpviewer_keywords:
 - code editor, find all references
@@ -15,7 +15,7 @@ ms.subservice: general-ide
 
 # Find references in your code
 
-You can use the **Find All References** command to determine where particular code elements are referenced throughout your codebase. The **Find All References** command is available on the context (right-click) menu of the element you want to find references to. You can also select the element and then select **Shift**+**F12**.
+You can use the **Find All References** command to determine where particular code elements are referenced throughout your codebase. In the code editor, the **Find All References** command is available on the context (right-click) menu of the element you want to find references to. You can also select the element and then select **Shift**+**F12**.
 
 The results appear in a tool window named **\<element> references**, where *element* is the name of the item you're searching for. A toolbar in the **references** window enables you to:
 

docs/msbuild/errors/msb3189.md

@@ -1,7 +1,7 @@
 ---
 title: "MSB3189 diagnostic code"
 description: Learn about the possible causes of the MSB3189 build error, and get troubleshooting tips.
-ms.date: 05/16/2025
+ms.date: 9/29/2025
 ms.topic: "error-reference"
 f1_keywords:
  - MSB3189
@@ -32,6 +32,9 @@ This article describes the MSB3189 error code.
 <!-- MSB3189: The update location for this application is a local path. -->
 
 <!-- :::editable-content name="postOutputDescription"::: -->
+## Description
+
+This error is given when the ClickOnce **Install location** is not in one of the supported formats. The string must be a fully qualified URL or UNC (Universal Naming Convention) path, for example, "http://www.contoso.com/myapplication" or "\\server\myapplication." Local paths and mapped network drives are not supported. In the **Publish** wizard, the relevant path is specified on the **Install location** page, which also appears on the **Publish** tab after you run the wizard to create a publish profile. In the `.pubxml` file, the element is `InstallUrl`. See [Specify ClickOnce Publish properties](../../deployment/how-to-specify-where-visual-studio-copies-the-files.md).
 <!--
 {StrBegin="MSB3189: "}
 -->

docs/msbuild/item-element-msbuild.md

@@ -1,7 +1,7 @@
 ---
 title: Item Element (MSBuild)
 description: Learn how MSBuild uses the Item element to contain a user-defined item and its metadata. Every item must be a child of an ItemGroup element.
-ms.date: 03/13/2017
+ms.date: 9/29/2025
 ms.topic: reference
 dev_langs:
 - VB
@@ -36,7 +36,7 @@ Contains a user-defined item and its metadata. Every item that is used in an MSB
 
 ## Specify metadata as attributes
 
-In MSBuild 15.1 or later, any metadata with a name that doesn't conflict with the current list of attributes can optionally be expressed as an attribute.
+You can specify item metadata as attributes for as child elements. Any metadata with a name that doesn't conflict with the current list of attributes can be expressed as an attribute.
 
 For example, to specify a list of NuGet packages, you would normally use something like the following syntax.
 
@@ -81,6 +81,8 @@ Now, however, you can pass the `Version` metadata as an attribute, such as in th
 |-------------|-----------------|
 |[ItemMetadata](../msbuild/itemmetadata-element-msbuild.md)|A user-defined item metadata key, which contains the item metadata value. There may be zero or more `ItemMetadata` elements in an item.|
 
+MSBuild interprets child elements on item elements as item metadata.
+
 ### Parent elements
 
 |Element|Description|