Merge pull request #10086 from MicrosoftDocs/main638448484166615265sync_temp

Repo sync for protected branch

Author: Jak-MS

.docutune/config/docutune-unattended.json

@@ -22,7 +22,10 @@
       "name": "Default",
       "command": "Fix",
       "configType": "full",
-      "stopAt": 25
+      "stopAt": 25,
+      "include": [
+        "docs/"
+      ]
     },
     {
       "name": "FlagBrokenLinks",

.docutune/config/docutune-visualstudio-docs-pr.json

@@ -35,15 +35,19 @@
     }
   ],
   "MetadataMultilineValues": true,
-,
-"RemoveTermSets": [
+  "RemoveTermSets": [
     "*right-click*",
     "*for-more-information-see*",
     "*had-had*",
 
     "formatting-learn-more",
-    "formatting-technical-for-more-information-see",
-    "formatting-technical-for-more-information-see-see",
-    "formatting-technical-accessibility-and-then-click"
+    "*and-then-click*",
+    "casing-product-windows-windows",
+    "invalid-abbreviation-ide-integrated-development-environment-0001-define-abbreviation*",
+    "invalid-abbreviation-ide-integrated-development-environment-0001-include-abbreviation*",
+    "*single-backtick*",
+    "*incorrect-backtick-spacing*",
+    "product-azure-app-service",
+    "*-caution-*"
   ]
 }

CONTRIBUTING.md

@@ -10,11 +10,11 @@ This project has adopted the [Microsoft Open Source Code of Conduct](https://ope
 
 ## How can I contribute?
 
-There is a variety of ways to contribute to the documentation. Review the sections below to find out which one is right for you.
+There is a variety of ways to contribute to the documentation. Review the following sections to find out which one is right for you.
 
 ### Report bugs or suggest enhancements
 
-Please use the feedback tool at the bottom of any article to submit bugs and suggestions.
+Use the feedback tool at the bottom of any article to submit bugs and suggestions.
 
 ![Feedback tool](media/feedback-tool.png)
 

README.md

@@ -14,7 +14,7 @@ The Learn site is changing how we receive feedback on the documentation. The new
 
 We welcome your contributions to help us improve the Visual Studio docs. All the articles in this repository use GitHub-flavored markdown.
 
-Several feature areas of Visual Studio have their own folders in this repo, such as **debugger** for topics on debugging, **ide** for topics on the Visual Studio interactive development environment (IDE), and so forth. The **/media** subfolder in each folder contains art files for the topics.
+Several feature areas of Visual Studio have their own folders in this repo, such as **debugger** for topics on debugging, **ide** for topics on the Visual Studio integrated development environment (IDE), and so forth. The **/media** subfolder in each folder contains art files for the topics.
 
 For more information about contributing, see the [Contributing guide](CONTRIBUTING.md).
 

SECURITY.md

@@ -4,38 +4,38 @@
 
 Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
 
-If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below.
+If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), report it to us as described below.
 
 ## Reporting Security Issues
 
 **Please do not report security vulnerabilities through public GitHub issues.**
 
-Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report).
+Instead, report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report).
 
-If you prefer to submit without logging in, send email to [[email protected]](mailto:[email protected]).  If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey).
+If you prefer to submit without logging in, send email to [[email protected]](mailto:[email protected]). If possible, encrypt your message with our Pretty Good Privacy (PGP) key; download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey).
 
-You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 
+You should receive a response within 24 hours. If for some reason you do not, follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc).
 
-Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
+Include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
 
-  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
-  * Full paths of source file(s) related to the manifestation of the issue
-  * The location of the affected source code (tag/branch/commit or direct URL)
-  * Any special configuration required to reproduce the issue
-  * Step-by-step instructions to reproduce the issue
-  * Proof-of-concept or exploit code (if possible)
-  * Impact of the issue, including how an attacker might exploit the issue
+  - Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, and so on)
+  - Full paths of source files related to the manifestation of the issue
+  - The location of the affected source code (tag/branch/commit or direct URL)
+  - Any special configuration required to reproduce the issue
+  - Step-by-step instructions to reproduce the issue
+  - Proof-of-concept code or exploit code (if possible)
+  - Impact of the issue, including how an attacker might exploit the issue
 
 This information will help us triage your report more quickly.
 
-If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs.
+If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs.
 
 ## Preferred Languages
 
 We prefer all communications to be in English.
 
 ## Policy
 
-Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd).
+Microsoft follows the principle of [Coordinated Vulnerability Disclosure (CVD)](https://aka.ms/opensource/security/cvd).
 
 <!-- END MICROSOFT SECURITY.MD BLOCK -->

docs/code-quality/how-to-enable-and-disable-automatic-code-analysis-for-managed-code.md

@@ -18,7 +18,7 @@ You can configure legacy code analysis (binary analysis) to run after each build
 
 To enable or disable legacy code analysis:
 
-1. In **Solution Explorer**, select and hold (or right-click) the project, and then select **Properties**.
+1. In **Solution Explorer**, right-click the project, and then select **Properties**.
 
 2. In the properties dialog box for the project, go to the **Code Analysis** tab.
 

docs/get-started/csharp/tutorial-aspnet-core.md

@@ -28,7 +28,7 @@ This tutorial shows you how to:
 
 ## Prerequisites
 
-You need Visual Studio to complete this tutorial. Visit the [Visual Studio downloads page](https://visualstudio.microsoft.com/vs) for a free version.
+You need Visual Studio to complete this tutorial. Visit the [Visual Studio downloads page](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-tutorial-create-csharp-aspnetcore-web-app-page-cta) for a free version.
 
 - For more information about upgrading to the latest Visual Studio release, see [Visual Studio updates](../../install/update-visual-studio.md).
 

docs/get-started/csharp/tutorial-console.md

@@ -32,7 +32,7 @@ In this tutorial, you complete the following tasks:
 
 You must have Visual Studio installed.
 
-If you haven't already installed Visual Studio, go to the [Visual Studio downloads](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-cta) page to install it for free.
+If you haven't already installed Visual Studio, go to the [Visual Studio downloads](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-tutorial-create-simple-csharp-console-app-page-cta) page to install it for free.
 
 ## Create a project
 

docs/ide/create-csharp-winform-visual-studio.md

@@ -18,7 +18,7 @@ In this tutorial, you'll create a simple C# application that has a Windows-based
 
 ::: moniker range="vs-2019"
 
-If you haven't already installed Visual Studio, go to the [Visual Studio downloads](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-cta) page to install it for free.
+If you haven't already installed Visual Studio, go to the [Visual Studio downloads](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-create-csharp-winform-app-page-cta) page to install it for free.
 
 > [!NOTE]
 > Some of the screenshots in this tutorial use the dark theme. If you aren't using the dark theme but would like to, see the [Change fonts, colors, and themes in Visual Studio](../ide/how-to-change-fonts-and-colors-in-visual-studio.md) page to learn how.
@@ -27,7 +27,7 @@ If you haven't already installed Visual Studio, go to the [Visual Studio downloa
 
 ::: moniker range="vs-2022"
 
-If you haven't already installed Visual Studio, go to the [Visual Studio 2022 downloads](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-cta) page to install it for free.
+If you haven't already installed Visual Studio, go to the [Visual Studio 2022 downloads](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download--create-csharp-winform-app-page-cta) page to install it for free.
 
 ::: moniker-end
 

docs/install/install-visual-studio.md

@@ -106,7 +106,7 @@ You will need to decide which version and edition of Visual Studio to install. T
 - The latest release of Visual Studio 2022 that is hosted on Microsoft servers. To install this, click on the following button and then choose the edition you want. A small "bootstrapper" file will then be downloaded into your **Downloads** folder.
 
  > [!div class="button"]
- > [Download Visual Studio](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-cta)
+ > [Download Visual Studio](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-install-visual-studio-page-cta)
 
 ::: moniker-end
 

docs/javascript/tutorial-asp-net-core-with-angular.md

@@ -30,7 +30,7 @@ You can use the method described in this article to create ASP.NET Core Single P
 
 Make sure to install the following:
 
-- Visual Studio 2022 version 17.8 or later with the **ASP.NET and web development** workload installed. Go to the [Visual Studio downloads](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-cta) page to install it for free.
+- Visual Studio 2022 version 17.8 or later with the **ASP.NET and web development** workload installed. Go to the [Visual Studio downloads](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-create-aspnetcore-app-with-angular-page-cta) page to install it for free.
   If you need to install the workload and already have Visual Studio, go to **Tools** > **Get Tools and Features...**, which opens the Visual Studio Installer. Choose the **ASP.NET and web development** workload, then choose **Modify**.
 - npm ([https://www.npmjs.com/](https://www.npmjs.com/package/npm)), which is included with Node.js
 - Angular CLI ([https://angular.io/cli](https://angular.io/cli))

docs/msbuild/build-process-overview.md

@@ -1,7 +1,7 @@
 ---
 title: How MSBuild builds projects
 description: Discover how MSBuild processes your project files, whether you invoke the build tool from Visual Studio or from a command line or script.
-ms.date: 05/18/2020
+ms.date: 02/13/2024
 ms.topic: overview
 helpviewer_keywords:
 - MSBuild, build process overview
@@ -18,21 +18,21 @@ The complete build process consists of [initial startup](#startup), [evaluation]
 
 ## Startup
 
-MSBuild can be invoked from Visual Studio through the MSBuild object model in *Microsoft.Build.dll*, or by invoking the executable directly on the command line, or in a script, such as in CI systems. In either case, inputs that affect the build process include the project file (or project object internal to Visual Studio), possibly a solution file, environment variables, and command-line switches or their object model equivalents. During the startup phase, the command-line options or object model equivalents are used to configure MSBuild settings such as configuring loggers. Properties set on the command line using the `-property` or `-p` switch are set as global properties, which override any values that would be set in the project files, even though project files are read in later.
+MSBuild can be invoked from Visual Studio through the MSBuild object model in *Microsoft.Build.dll*, or by invoking the executable (`MSBuild.exe` or `dotnet build`) directly on the command line, or in a script, such as in CI systems. In either case, inputs that affect the build process include the project file (or project object internal to Visual Studio), possibly a solution file, environment variables, and command-line switches or their object model equivalents. During the startup phase, the command-line options or object model equivalents are used to configure MSBuild settings such as configuring loggers. Properties set on the command line using the `-property` or `-p` switch are set as global properties, which override any values that would be set in the project files, even though project files are read in later.
 
 The next sections are about the input files, such as solution files or project files.
 
 ### Solutions and projects
 
 MSBuild instances may consist of one project, or many projects as part of a solution. The solution file isn't an MSBuild XML file, but MSBuild interprets it to know all the projects that are required to be built for the given configuration and platform settings. When MSBuild processes this XML input, it's referred to as the solution build. It has some extensible points that allow you to run something at every solution build, but since this build is a separate run from the individual project builds, no settings of properties or target definitions from the solution build are relevant to each project build.
 
-You can find out how to extend the solution build at [Customize the solution build](customize-your-build.md#customize-the-solution-build).
+You can find out how to extend the solution build at [Customize the solution build](customize-solution-build.md).
 
 ### Visual Studio builds vs. MSBuild.exe builds
 
 There are some significant differences between when projects build in Visual Studio vs. when you invoke MSBuild directly, either through the MSBuild executable, or when you use the MSBuild object model to start a build. Visual Studio manages the project build order for Visual Studio builds; it only calls MSBuild at the individual project level, and when it does, a couple of Boolean properties (`BuildingInsideVisualStudio`, `BuildProjectReferences`) are set that significantly affect what MSBuild does. Inside each project, execution occurs the same as when invoked through MSBuild, but the difference arises with referenced projects. In MSBuild, when referenced projects are required, a build actually occurs; that is, it runs tasks and tools, and generates the output. When a Visual Studio build finds a referenced project, MSBuild only returns the expected outputs from the referenced project; it lets Visual Studio control the building of those other projects. Visual Studio determines the build order and calls into MSBuild separately (as needed), all completely under Visual Studio's control.
 
-Another difference arises when MSBuild is invoked with a solution file, MSBuild parses the solution file, creates a standard XML input file, evaluates it, and executes it as a project. The solution build is executed before any project. When building from Visual Studio, none of this happens; MSBuild never sees the solution file. As a consequence, solution build customization (using *before.SolutionName.sln.targets* and *after.SolutionName.sln.targets*) only applies to MSBuild.exe or object model driven, not Visual Studio builds.
+Another difference arises when MSBuild is invoked with a solution file, MSBuild parses the solution file, creates a standard XML input file, evaluates it, and executes it as a project. The solution build is executed before any project. When building from Visual Studio, none of this happens; MSBuild never sees the solution file. As a consequence, solution build customization (using *before.SolutionName.sln.targets* and *after.SolutionName.sln.targets*) only applies to MSBuild.exe, `dotnet build`, or object-model-driven builds, not Visual Studio builds.
 
 ### Project SDKs
 
@@ -91,7 +91,7 @@ In this phase, all target object structures are created in memory, in preparatio
 
 ## Execution phase
 
-In the execution phase, the targets are ordered and run, and all tasks are executed. But first, properties and items that are defined within targets are evaluated together in a single phase in the order in which they appear. The order of processing is notably different from how  properties  and items that aren't in a target are processed: all properties first, and then all items, in separate passes. Changes to properties and items within a target can be observed after the target where they were changed.
+In the execution phase, the targets are ordered and run, and all tasks are executed. But first, properties and items that are defined within targets are evaluated together in a single phase in the order in which they appear. The order of processing is notably different from how properties and items that aren't in a target are processed: all properties first, and then all items, in separate passes. Changes to properties and items within a target can be observed after the target where they were changed.
 
 ### Target build order