Merge pull request #13701 from MicrosoftDocs/ghogen-patch-95

Recommend using project references instead of project dependencies

Author: prmerger-automator[bot]

docs/ide/how-to-create-and-remove-project-dependencies.md

@@ -1,7 +1,7 @@
 ---
 title: 'Create and remove project dependencies'
 description: Create and remove your project's dependency on code from other projects in Visual Studio, and view the build order for the solution.
-ms.date: 03/14/2024
+ms.date: 03/12/2025
 ms.topic: how-to
 f1_keywords:
 - VS.ProjectDependenciesDlg
@@ -22,7 +22,7 @@ manager: mijacobs
 When building a solution that contains multiple projects, it can be necessary to build certain projects first, to generate compiled binaries used by other projects. When a project consumes output generated by another project, the project that generates the output is referred to as a project dependency of the project that consumes the output. Such dependency relationships can be defined in the **Project Dependencies** dialog box.
 
 > [!TIP]
-> A project dependency is automatically created when you add a project-to-project reference from one project to another project. Before you perform these steps, consider if you should instead create a project-to-project reference, which in addition to creating a dependency relationship between the projects, also creates a reference that you can use to build code that uses classes, interfaces, and other code entities from the other project. See [Managing references in a project](managing-references-in-a-project.md#project-to-project-references).
+> The feature discussed in this article, manually managing project dependencies, is distinct from project-to-project references used in modern project types, and reflects a method of handling dependencies between projects that predates MSBuild. Unless you're working with a project type that doesn't support project-to-project references, it's not necessary to explicitly add project dependencies as described in this article. A project dependency is automatically created when you add a project-to-project reference from one project to another project. In most cases, you should instead create a project-to-project reference, which in addition to creating a dependency relationship between the projects, also creates a reference that you can use to build code that uses classes, interfaces, and other code entities from the other project. See [Managing references in a project](managing-references-in-a-project.md#project-to-project-references).
 
 ## To assign dependencies to projects