Merge pull request #10691 from MicrosoftDocs/main638792126270157806sync_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/containers/edit-and-refresh.md

@@ -5,7 +5,7 @@ ms.author: ghogen
 author: ghogen
 manager: mijacobs
 ms.topic: how-to
-ms.date: 04/26/2024
+ms.date: 4/1/2025
 ms.subservice: container-tools
 ---
 

docs/ide/finding-references.md

@@ -1,7 +1,7 @@
 ---
 title: Finding references in your code
 description: Explore the Find All References command in Visual Studio to find references to particular code elements in your code, including by reference type.
-ms.date: 04/10/2024
+ms.date: 4/1/2025
 ms.topic: conceptual
 helpviewer_keywords:
 - code editor, find all references
@@ -23,11 +23,17 @@ The results appear in a tool window named **\<element> references**, where *elem
 - Remove any filters on the returned results by choosing the **Clear All Filters** button.
 - Change how returned items are grouped by choosing a setting in the **Group by:** drop-down list box.
 - Keep the current search results window by choosing the **Keep Results** button. When you choose this button, the current search results stay in this window, and new search results appear in a new tool window.
+- **List View** toggles between the treeview and a plaintext list. Some functionality is disabled in list view mode.
 - Search for strings within the search results by entering text in the **Search Find All References** text box.
 
 You can also hover the mouse over any search result to see the reference in the context of the surrounding code.
 
+:::moniker range="vs-2019"
 ![Screenshot of the Find All References tool window.](../ide/media/vside_findallreferences.png)
+:::moniker-end
+:::moniker range="vs-2022"
+![Screenshot of the Find All References tool window.](media/vs-2022/find-all-references.png)
+:::moniker-end
 
 ## Navigate to references
 
@@ -43,12 +49,18 @@ By default, references are grouped by project, then by definition. However, you
 
 **Definition** and **Project** are the two default groupings used, but you can add others by choosing the **Grouping** command on the selected item's right-click or context menu. Adding more groupings can be helpful if your solution has numerous files and paths.
 
+Grouping is not available in **List View** mode.
+
 ## Filter by reference type in .NET
 
-In C# or Visual Basic, the **Find References** window has a **Kind** column where it lists what type of reference it found. You can use this column to filter by reference type. Select the filter icon that appears when you hover over the column header. You can filter references by Read, Write, Reference, Name, Namespace, and Type.
+In C# or Visual Basic, the **Find References** window has a **Kind** column where it lists what type of reference it found. You can use this column to filter by reference type. Select the filter icon that appears when you hover over the column header. You can filter references by Read, Write, Reference, Name, Namespace, and Type, but the filter only shows the kinds that are relevant in the current set of results.
 
+:::moniker range="vs-2019"
 ![Screenshot of the Find References window that highlights the Kind column.](../ide/media/vside_findallreferencesKind.png)
-
+:::moniker-end
+:::moniker range=">=vs-2022"
+![Screenshot of the Find References window that highlights the Kind column.](media/vs-2022/find-all-references-kind-filter.png)
+:::moniker-end
 After you apply a filter or a filter set, you can easily remove it by using the **Clear All Filters** button.
 
 ## Customize the experience

docs/ide/how-to-create-multi-project-templates.md

@@ -1,7 +1,7 @@
 ---
 title: Create multi-project templates
 description: Create multi-project templates in Visual Studio that can act as containers for many projects at the same time and containers for projects of different languages.
-ms.date: 04/05/2024
+ms.date: 04/01/2025
 ms.topic: how-to
 helpviewer_keywords:
 - Visual Studio templates, creating multi-project

docs/ide/how-to-exclude-projects-from-a-build.md

@@ -1,7 +1,7 @@
 ---
 title: 'Exclude projects from a build'
 description: Exclude projects from a build in Visual Studio by building the solution without building all projects contained in the solution.
-ms.date: 05/15/2024
+ms.date: 4/1/2025
 ms.subservice: compile-build
 ms.topic: how-to
 author: ghogen

docs/ide/intellicode-visual-studio.md

@@ -2,7 +2,7 @@
 title: IntelliCode for Visual Studio
 titleSuffix: ""
 description: Read an overview of IntelliCode for Visual Studio. Understand preview features, supported languages, prerequisites, troubleshooting issues, and telemetry.
-ms.date: 10/04/2023
+ms.date: 4/1/2025
 ms.service: visual-studio-family
 ms.subservice: intellicode
 ms.topic: conceptual

docs/ide/media/vs-2022/find-all-references-kind-filter.png

@@ -1,6 +1,6 @@
 ---
 title: IntelliCode Whole-line autocompletions 
-ms.date: 9/26/2023
+ms.date: 4/1/2025
 ms.service: visual-studio-family
 ms.subservice: intellicode
 ms.topic: conceptual

docs/ide/media/vs-2022/find-all-references.png

@@ -1,7 +1,7 @@
 ---
 title: Common MSBuild Project Items
 description: Learn about common MSBuild project items. Items are named references to one or more files, and have metadata like file names, paths, and version numbers.
-ms.date: 10/29/2020
+ms.date: 4/2/2025
 ms.topic: reference
 dev_langs:
 - VB
@@ -18,7 +18,7 @@ ms.subservice: msbuild
 
 In MSBuild, an item is a named reference to one or more files. Items contain metadata such as file names, paths, and version numbers. All project types in Visual Studio have several items in common. These items are defined in the file *Microsoft.Build.CommonTypes.xsd*.
 
-This article lists all the common project items.
+This article lists all the common project items defined in MSBuild itself. Items and properties provided by the .NET SDK are documented at [MSBuild reference for Microsoft.Net.Sdk](/dotnet/core/project-sdk/msbuild-props).
 
 ## `Reference`
 

docs/ide/visual-studio-whole-line-completions.md

@@ -132,6 +132,8 @@ ms.subservice: msbuild
 
 The following table lists frequently used properties that are defined in the Visual Studio project files or included in *.targets* files that MSBuild provides.
 
+Properties provided by the .NET SDK are documented at [MSBuild reference for Microsoft.Net.Sdk](/dotnet/core/project-sdk/msbuild-props).
+
 Project files in Visual Studio (*.csproj*, *.vbproj*, *.vcxproj*, and others) contain MSBuild XML code that runs when you build a project by using the IDE. Projects typically import one or more *.targets* files to define their build process. For more information, see [MSBuild .targets files](../msbuild/msbuild-dot-targets-files.md).
 
 When setting property values, keep in mind that common properties may be set, reset, or used in a number of imported files. Therefore, it matters where you set a property--in your project file, in *Directory.Build.props*, or in another imported file. If you're setting a property somewhere and not getting the expected result, consider where and how the property is changed or used in all the files imported by your project, including imports that are added implicitly when you're using the `Sdk` attribute. See [Choose between adding properties to a .props or .targets file](customize-your-build.md#choose-between-adding-properties-to-a-props-or-targets-file). Preprocessing can help with this (see the `/preprocess` or `/pp` command-line option at [MSBuild command-line reference](./msbuild-command-line-reference.md)).