Repo sync for protected branch

docs/ide/dotfuscator/index.md

@@ -383,7 +383,7 @@ See [the full Dotfuscator Community User Guide at preemptive.com][full] for deta
 [attributes-checks]: https://www.preemptive.com/dotfuscator/ce/docs/help/attributes_checks.html
 [attributes-obfuscation]: https://www.preemptive.com/dotfuscator/ce/docs/help/attributes_obfuscation.html
 
-[verbosity]: ../how-to-view-save-and-configure-build-log-files.md#to-change-the-amount-of-information-included-in-the-build-log
+[verbosity]: ../how-to-view-save-and-configure-build-log-files.md#specify-data-verbosity-for-build-logs
 [dotnet-attributes]: /dotnet/standard/attributes
 [application-insights]: /azure/azure-monitor/app/app-insights-overview
 [nuget-org]: https://www.nuget.org/

docs/ide/how-to-locate-and-organize-project-and-item-templates.md

@@ -1,8 +1,8 @@
 ---
 title: Locate and organize project templates
-description: Locate and organize project templates, including installed templates and user templates (.vstemplate files), in Visual Studio.
-ms.date: 11/15/2022
-ms.topic: how-to
+description: Locate and organize project and item templates in Visual Studio, including installed templates and user templates (.vstemplate files).
+ms.date: 08/21/2024
+ms.topic: concept-article
 helpviewer_keywords:
 - project templates [Visual Studio], locations
 - item templates [Visual Studio], locations
@@ -11,18 +11,21 @@ author: ghogen
 ms.author: ghogen
 manager: mijacobs
 ms.subservice: general-ide
+
+#customer intent: As a developer, I want to locate and organize project and item templates in Visual Studio, so I can easily access them to create code for new projects and items.
 ---
+
 # Locate and organize project and item templates
 
-Template files must be placed in a known location in order for them to be shown in the new project and new item dialog boxes..
+When template files are placed in a known location, Visual Studio can locate the files and make them available for creating new projects and new items. Templates provide a convenient way to create applications, access class libraries, implement unit tests, and set up configuration files.
 
-## Locate templates
+Installed templates and user templates (*.vstemplate* files) are stored in different locations. You can also customize the locations with Visual Studio options.
 
-Installed templates and user templates are stored in two different locations.
+This article describes the template file locations recognized by Visual Studio.
 
-### Installed templates
+## Location for installed templates
 
-By default, templates installed with Visual Studio are located in:
+By default, templates installed with Visual Studio are placed in the following locations:
 
 ::: moniker range="vs-2019"
 
@@ -35,7 +38,6 @@ For example, the following directory has the Visual Basic item templates for Eng
 *C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\Common7\\IDE\\ItemTemplates\\VisualBasic\\1033*
 
 ::: moniker-end
-
 ::: moniker range="vs-2022"
 
 - *%ProgramFiles%\\Microsoft Visual Studio\\2022\\\<edition>\\Common7\IDE\ProjectTemplates\\<Language\>\\<Locale ID\>*
@@ -48,9 +50,9 @@ For example, the following directory has the Visual Basic item templates for Eng
 
 ::: moniker-end
 
-### User templates
+## Location for user templates
 
-If you add a compressed (*.zip*) file that includes a *.vstemplate* file to the user template directory, the template appears in the new project and new item dialog boxes. By default, user templates are located in:
+When you add a compressed (*.zip*) file that includes a *.vstemplate* file to the user template directory, Visual Studio makes the template available in the **New project** and **New item** dialogs. By default, user templates are placed in the following locations:
 
 ::: moniker range="vs-2019"
 
@@ -76,18 +78,12 @@ For example, the following directory has user project templates for C#:
 
 ::: moniker-end
 
-> [!TIP]
-> You can change the known location for user templates in **Tools** > **Options** > **Projects and Solutions** > **Locations**.
-
-## Next steps
-
-To learn more about .NET SDK templates and their locations, reference the following articles.
+### Change location for user templates
 
-|Article  |Description  |
-|---------|---------|
-|[.NET default templates](/dotnet/core/tools/dotnet-new-sdk-templates) | When you install the .NET SDK, you receive over a dozen built-in templates for creating projects and files, including console apps, class libraries, unit test projects, ASP.NET Core apps (including Angular and React projects), and configuration files.  This article lists the templates that come pre-installed with the .NET SDK and describes how to interact with them. |
-|[Manage .NET project and item templates](/dotnet/core/install/templates?pivots=os-windows&preserve-view=true) | .NET provides a template system that enables users to install or uninstall packages containing templates from NuGet, a NuGet package file, or a file system directory. This article describes how to manage .NET templates through the .NET SDK CLI. |
+You can change the location for user templates in Visual Studio with the **Tools** > **Options** dialog. The location settings are on the **Projects and Solutions** > **Locations** page.
 
 ## Related content
 
-- [Visual Studio template schema reference (extensibility)](../extensibility/visual-studio-template-schema-reference.md)
+- Review the [Visual Studio template schema reference (extensibility)](../extensibility/visual-studio-template-schema-reference.md)
+- Use [prebuilt templates installed with the .NET SDK](/dotnet/core/tools/dotnet-new-sdk-templates)
+- [Manage .NET project and item templates with the .NET SDK CLI](/dotnet/core/install/templates?pivots=os-windows&preserve-view=true)

docs/ide/how-to-view-save-and-configure-build-log-files.md

@@ -1,78 +1,100 @@
 ---
-title: 'View, save, and configure build log files'
-description: View, save, and configure build log files that contain information such as the command lines used for the compiler and other tools, and troubleshoot build failures.
-ms.date: 11/11/2022
+title: View, save, and configure build log files
+description: Explore how to configure build log files with information about the compiler and other tools for troubleshooting build failures.
+ms.date: 08/21/2024
 ms.subservice: compile-build
 ms.topic: how-to
 author: ghogen
 ms.author: ghogen
 manager: mijacobs
+
+#customer intent: As a developer, I want to work with build log files in Visual Studio so I can troubleshoot build failures.
 ---
+
 # View, save, and configure build log files
 
-After you build a project in the Visual Studio IDE, you can view information about that build in the **Output** window. By using this information, you can troubleshoot a build failure, view the exact command lines used for all the build tools, or get full diagnostic information about the entire build process.
+After you build a project in the Visual Studio Interactive Development Environment (IDE), you can view logged information about the build in the Visual Studio **Output** window. The output data can be saved to log files that you can view in Visual Studio and other editors. 
+
+The logs can help you troubleshoot issues in the build. You can locate the exact command lines used for all build tools, and get full diagnostic data about the entire build process. Visual Studio provides options to specify the kinds of information you want to see in the build output and build log files.
+
+This article describes how to generate, configure, and view build log files in Visual Studio.
+
+## Generate and view build log files
+
+Use the following procedures to generate and view build log files for your scenario.
 
-- For C++ projects, you can also view the same information in a log file that's created and saved when you build a project.
+- **C++ project**:
 
-- For .NET projects, you can click in the build output window and press **Ctrl**+**S**. Visual Studio prompts you for a location to save the information from the **Output** window into a log file.
+   Visual Studio saves the log files for you when you build your project. Common locations for the log files include *Release\\\<ProjectName>.log*, *Debug\\\<ProjectName>.log*, and *\<ProjectName>.txt*. All file locations are relative to your project root folder and based on your specific configuration.
 
-You can also use the IDE to specify what kinds of information you want to view about each build.
+   1. Use **Windows Explorer** or **File Explorer** to browse to the log file.
+
+   1. Open the log file in your preferred editor.
 
-If you build any kind of project by using MSBuild, you can create a log file to save information about the build. For more information, see [Obtain build logs](../msbuild/obtaining-build-logs-with-msbuild.md).
+- **.NET project**:
 
-## To view the build log file for a C++ project
+   For .NET projects, you instruct Visual Studio to save the log files:
 
-1. In **Windows Explorer** or **File Explorer**, open the following file (relative to the project root folder): *Release\\{ProjectName}.Log* or *Debug\\{ProjectName}.log*
+   1. In Visual Studio, select **Build** > **Build Solution**.
 
-## To create a build log file for a managed-code project
+   1. In the **Output** window, select in the text and use the **Ctrl**+**S** keyboard shortcut.
+
+   Visual Studio prompts you for a location to save the build output. You can then open the log files from that location in Visual Studio or another editor.
 
-1. On the menu bar, choose **Build** > **Build Solution**.
+- **MSBuild**:
 
-2. In the **Output** window, click somewhere in the text.
+   You can generate build logs by running MSBuild directly from the command line by using the `-fileLogger` (`-fl`) command-line option. For more information, see [Obtain build logs with MSBuild](../msbuild/obtaining-build-logs-with-msbuild.md).
 
-3. Press **Ctrl**+**S**.
+## Specify data verbosity for build logs
 
-   Visual Studio prompts you for a location to save the build output.
+You can specify how much information to include in the build log files. The amount of data in the log file columns is measured as *logger verbosity*. The number of log file rows represent *messages collected*. The log verbosity (column values) affects the types of logged messages (row values). **Quiet** verbosity produces minimal logging in the build output. **Diagnostic** is the most verbose setting and generates log files with all possible data.
 
-You can also generate logs by running MSBuild directly from the command line, using the `-fileLogger` (`-fl`) command-line option. See [Obtain build logs with MSBuild](../msbuild/obtaining-build-logs-with-msbuild.md).
+The following table shows what types of messages are collected based on the logger verbosity:
 
-## To change the amount of information included in the build log
+| Message type / Verbosity           | Quiet | Minimal | Normal | Detailed | Diagnostic |
+|------------------------------------|:-----:|:-------:|:------:|:--------:|:----------:|
+| Errors                             |  ✅   |   ✅   |   ✅   |   ✅    |    ✅     |
+| Warnings                           |  ✅   |   ✅   |   ✅   |   ✅    |    ✅     |
+| High-importance messages           |       |   ✅   |   ✅   |    ✅    |    ✅     |
+| Normal-importance messages         |       |         |   ✅   |   ✅    |    ✅     |
+| Low-importance messages            |       |         |        |    ✅    |    ✅     |
+| Other MSBuild-engine information   |       |         |        |          |    ✅     |
 
-1. On the menu bar, choose **Tools** > **Options**.
+You can configure the logger verbosity with the following steps:
 
-2. On the **Projects and Solutions** page, choose the **Build and Run** page.
+1. In Visual Studio, select **Tools** > **Options** to open the **Options** dialog.
 
-3. In the **MSBuild project build output verbosity** list, choose one of the values, and then choose the **OK** button.
+1. On the dialog, expand the **Projects and Solutions** section and select the **Build and Run** tab.
 
-The following table shows how the log verbosity (column values) affects which types of message (row values) are logged.
+1. Use the **MSBuild project build output verbosity** dropdown list and select your build output preference. 
 
-| Message type / Verbosity              | Quiet | Minimal | Normal | Detailed | Diagnostic |
-|---------------------------------------|:-----:|:-------:|:------:|:--------:|:----------:|
-| Errors                                |   ✅   |    ✅    |    ✅   |     ✅    |      ✅     |
-| Warnings                              |   ✅   |    ✅    |    ✅   |     ✅    |      ✅     |
-| High-importance Messages              |       |    ✅    |    ✅   |     ✅    |      ✅     |
-| Normal-importance  Messages           |       |         |    ✅   |     ✅    |      ✅     |
-| Low-importance  Messages              |       |         |        |     ✅    |      ✅     |
-| Additional MSBuild-engine information |       |         |        |          |      ✅     |
+1. Use the **MSBuild project build log file verbosity** dropdown list and select your logger verbosity preference. 
 
-If you want to see the command lines used for the compiler and other tools, choose at least the **Detailed** verbosity level.
+   > [!TIP]
+   > If you want to see the command lines used for the compiler and other tools, choose at least the **Detailed** verbosity level.
 
-For more information, see [Options dialog box,  Projects and Solutions, Build and Run](../ide/reference/options-dialog-box-projects-and-solutions-build-and-run.md) and <xref:Microsoft.Build.Framework.LoggerVerbosity>.
+1. To apply your changes, select **OK**.
 
 > [!IMPORTANT]
-> You must rebuild the project for your changes to take effect in the **Output** window (all projects) and the *\<ProjectName>.txt* file (C++ projects only).
+> You must rebuild the project for your changes to take effect in the **Output** window. For C++ projects, the project rebuild also ensures the changes are reflected in the *\<ProjectName>.txt* file.
 
-## Use binary logs to make it easier to browse large log files
+For more information, see [Options dialog box, Projects and Solutions, Build and Run](./reference/options-dialog-box-projects-and-solutions-build-and-run.md) and <xref:Microsoft.Build.Framework.LoggerVerbosity>.
+
+## Use binary logs for large log files
 
 :::moniker range="<=vs-2019"
+
 Binary logs are an optional feature for .NET projects that lets you have a richer log browsing experience that might make it easier to find information in large logs. To use binary logs, install the [Project System Tools](https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.ProjectSystemTools). For more information, see [`https://msbuildlog.com`](https://msbuildlog.com) and [Binary Log](https://github.com/microsoft/msbuild/blob/master/documentation/wiki/Binary-Log.md).
+
 :::moniker-end
 :::moniker range=">=vs-2022"
+
 Binary logs are an optional feature for .NET projects that lets you have a richer log browsing experience that might make it easier to find information in large logs. To use binary logs, install the [Project System Tools 2022](https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.ProjectSystemTools2022). For more information, see [`https://msbuildlog.com`](https://msbuildlog.com) and [Binary Log](https://github.com/microsoft/msbuild/blob/master/documentation/wiki/Binary-Log.md).
+
 :::moniker-end
 
 ## Related content
 
-- [Build and clean projects and solutions in Visual Studio](../ide/building-and-cleaning-projects-and-solutions-in-visual-studio.md)
-- [Compile and build](../ide/compiling-and-building-in-visual-studio.md)
-- [Obtaining build logs with MSBuild](../msbuild/obtaining-build-logs-with-msbuild.md)
+- [Build and clean projects and solutions in Visual Studio](building-and-cleaning-projects-and-solutions-in-visual-studio.md)
+- [Compile and build](compiling-and-building-in-visual-studio.md)
+- [Obtain build logs with MSBuild](../msbuild/obtaining-build-logs-with-msbuild.md)