MicrosoftDocs · learn-build-service-prod · Nov 15, 2024 · Nov 1, 2024 · Nov 13, 2024 · Nov 13, 2024
diff --git a/docs/data-tools/add-new-connections.md b/docs/data-tools/add-new-connections.md
@@ -1,6 +1,6 @@
 ---
 title: Connect to database or open MDF file (ADO.NET)
-ms.date: 11/09/2023
+ms.date: 11/14/2024
 description: Connect to a database or data service with ADO.NET in Visual Studio, or connect to a database opened from a median disk file (.mdf).
 ms.topic: how-to
 author: ghogen

diff --git a/docs/deployment/deploying-applications-services-and-components.md b/docs/deployment/deploying-applications-services-and-components.md
@@ -1,7 +1,7 @@
 ---
 title: "First look at deployment"
 description: Explore application deployment options in Visual Studio, including Azure, the web, network shares, devices, Microsoft Store, and Windows desktop installer packages.
-ms.date: 11/02/2023
+ms.date: 11/14/2024
 ms.topic: conceptual
 dev_langs:
   - "FSharp"
@@ -85,10 +85,10 @@ If you require a more complex installation of a desktop application than ClickOn
 
 - An MSI or EXE installer package can be created by using a Setup project (vdproj). To use this option, see [Visual Studio Installer Projects Extension and .NET 6.0](../deployment/installer-projects-net-core.md) or, go directly to the [Visual Studio Installer Projects extension](https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.MicrosoftVisualStudio2017InstallerProjects#overview).
 
-- An MSI or EXE installer package can be created by using [InstallShield](https://www.revenera.com/install/products/installshield/installshield-requirements) from Flexera Software. InstallShield may be used with Visual Studio 2017 and later versions. Community Edition isn't supported.
+- An MSI or EXE installer package can be created by using [InstallShield](https://www.revenera.com/install/products/installshield/installshield-requirements) from Revenera Software. InstallShield may be used with Visual Studio 2017 and later versions. Community Edition isn't supported.
 
   > [!NOTE]
-  > InstallShield Limited Edition is no longer included with Visual Studio and isn't supported in Visual Studio 2017 and later versions. Check with Flexera Software about future availability.
+  > InstallShield Limited Edition is no longer included with Visual Studio and isn't supported in Visual Studio 2017 and later versions. Check with Revenera Software about future availability.
 
 - You can also install prerequisite components for desktop applications by configuring a generic installer package, which is known as a bootstrapper. For more information, see [Application deployment prerequisites](../deployment/application-deployment-prerequisites.md).
 :::moniker-end
@@ -99,12 +99,12 @@ If you require a more complex installation of a desktop application than ClickOn
 
 - An MSI-based installer package can be created by using the [WiX Toolset Visual Studio 2022 Extension](https://marketplace.visualstudio.com/items?itemName=WixToolset.WixToolsetVisualStudio2022Extension). This is a command-line toolset.
 
-- An MSI or EXE installer package can be created by using a Setup project (vdproj). To use this option, see [Visual Studio Installer Projects Extension and .NET 6.0](../deployment/installer-projects-net-core.md) or, go directly to the [Visual Studio Installer Projects extension](https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.MicrosoftVisualStudio2017InstallerProjects#overview).
+- An MSI or EXE installer package can be created by using a Setup project (vdproj). To use this option, see [Visual Studio Installer Projects Extension and .NET 6.0](../deployment/installer-projects-net-core.md) or, go directly to the [Visual Studio Installer Projects extension](https://marketplace.visualstudio.com/items?itemName=VisualStudioClient.MicrosoftVisualStudio2022InstallerProjects).
 
-- An MSI or EXE installer package can be created by using [InstallShield](https://www.revenera.com/install/products/installshield/installshield-requirements) from Flexera Software. InstallShield may be used with Visual Studio 2017 and later versions. Community Edition isn't supported.
+- An MSI or EXE installer package can be created by using [InstallShield](https://www.revenera.com/install/products/installshield/installshield-requirements) from Revenera Software. InstallShield may be used with Visual Studio 2017 and later versions. Community Edition isn't supported.
 
   > [!NOTE]
-  > InstallShield Limited Edition is no longer included with Visual Studio and isn't supported in Visual Studio 2017 and later versions. Check with Flexera Software about future availability.
+  > InstallShield Limited Edition is no longer included with Visual Studio and isn't supported in Visual Studio 2017 and later versions. Check with Revenera Software about future availability.
 
 - You can also install prerequisite components for desktop applications by configuring a generic installer package, which is known as a bootstrapper. For more information, see [Application deployment prerequisites](../deployment/application-deployment-prerequisites.md).
 :::moniker-end

diff --git a/docs/deployment/installer-projects-net-core.md b/docs/deployment/installer-projects-net-core.md
@@ -2,7 +2,7 @@
 title: "Visual Studio Installer Projects and .NET"
 description: Explore how to use the Visual Studio Installer Projects Extension to package .NET Core 3.1 or .NET 5 and later version applications for Microsoft Installer (MSI).
 titleSuffix: ""
-ms.date: "03/13/2024"
+ms.date: "11/13/2024"
 ms.topic: "conceptual"
 helpviewer_keywords:
   - "installer projects"
@@ -17,7 +17,7 @@ monikerRange: '>= vs-2019'
 
 Packaging applications as an MSI is often accomplished using the Visual Studio Installer Projects Extension.
 
-This article applies to apps targeting .NET Core 3.1, .NET 5, .NET 6, and later.
+This article applies to apps targeting .NET Core 3.1 and .NET 5 or later versions.
 
 You can download the extension here:
 
@@ -52,13 +52,20 @@ To learn more about these deployment strategies, see [.NET application publishin
 
 ### Workflow changes for .NET Core 3.1 and .NET 5 or later
 
-1. Select **Publish Items** instead of **Primary Output** to get the correct output for .NET Core 3.1 and .NET 5.0 or later projects.  To bring up this dialog, select **Add** > **Project Output...** from the project's context menu.
+- To get the correct output for .NET Core 3.1 and .NET 5.0 or later projects, select **Publish Items** instead of **Primary Output** in the **Add Project Output Group** dialog box.  To open this dialog, select **Add** > **Project Output...** from the Setup project's context menu.
 
-    ![The Publish Items output group in the Add Project Output Group dialog](../deployment/media/installer-projects-net-core-publish-items-output.png "Pick Publish Items")
+  ![The Publish Items output group in the Add Project Output Group dialog](../deployment/media/installer-projects-net-core-publish-items-output.png "Pick Publish Items")
 
-2. To create a self-contained installer, set the **PublishProfilePath** property on the **Publish Items** node in the setup project, using the relative path of a publish profile with the correct properties set.
+- To create a self-contained installer, set the **PublishProfilePath** property on the **Publish Items** node in the Setup project, using the relative path of a publish profile with the correct properties set.
 
-    ![Setting the publish profile on the Publish Items project output item](../deployment/media/installer-projects-net-core-publish-profile.png "Set Publish Profile")
+  ::: moniker range=">= vs-2022"
+  :::image type="content" source="../deployment/media/vs-2022/installer-projects-net-core-publish-profile.png" border="false" alt-text="Screenshot that shows setting the publish profile on the Publish Items project output item." lightbox="../deployment/media/vs-2022/installer-projects-net-core-publish-profile.png":::
+  ::: moniker-end
+  ::: moniker range="vs-2019"
+  ![Screenshot of setting the publish profile on the Publish Items project output item.](../deployment/media/installer-projects-net-core-publish-profile.png "Set Publish Profile")
+  ::: moniker-end
+
+  Before you can set this property, create a publish profile from the application project by choosing **Publish** from the application project's context menu in Solution Explorer, and deploy the application to a folder.
 
 >[!NOTE]
 >This workflow is not supported for ASP.NET Core applications, only Windows Desktop applications.
@@ -69,7 +76,7 @@ If you would like your installer to be able to install the necessary runtime for
 
 ![.NET Core items in the Prerequisites dialog](../deployment/media/installer-projects-net-core-prerequisites.png ".NET Core Prerequisites")
 
-The **.NET Core Runtime...** option should be selected for console applications, **.NET Desktop Runtime...** should be selected for WPF/WinForms applications.
+The **.NET Core Runtime...** option should be selected for console applications, **.NET Desktop Runtime...** should be selected for WPF and WinForms applications.
 
 >[!NOTE]
 >These items are present starting with the Visual Studio 2019 Update 7 release.

diff --git a/docs/deployment/media/vs-2022/installer-projects-net-core-publish-profile.png b/docs/deployment/media/vs-2022/installer-projects-net-core-publish-profile.png
diff --git a/docs/ide/how-to-specify-build-events-csharp.md b/docs/ide/how-to-specify-build-events-csharp.md
@@ -36,7 +36,7 @@ Use build events to specify commands that run before the build starts or after t
 5. In the **Post-build event command line** box, specify the syntax of the build event.
 
    > [!NOTE]
-   > Add a `call` statement before all post-build commands that run *.bat* files. For example, `call MyFile.bat` or `call MyFile.bat call MyFile2.bat`. Paths can be absolute, or relative to the project folder.
+   > Add a `call` statement before all post-build commands that run *.bat* files. For example, `call MyFile.bat` or `call MyFile.bat call MyFile2.bat`. Paths can be absolute, or relative to the output folder.
 
 6. In the **Run the post-build event** box, specify under what conditions to run the post-build event.
 

diff --git a/docs/ide/reference/error-list-window.md b/docs/ide/reference/error-list-window.md
@@ -61,6 +61,10 @@ The list on the right side of the toolbar specifies whether to show errors from
 
 Use the **Search Error List** text box on the right side of the **Error List** toolbar to find specific errors in the error list. You can search on any visible column in the error list, and search results are always sorted based on the column that has sort priority instead of on the query or the filter applied. If you choose the **Esc** key while the focus is in the **Error List**, you can clear the search term and filtered search results. You can also click the **X** on the right side of the text box to clear it.
 
+## Search online
+
+To get information about an error, press **F1** to bring up the error's page in the documentation. If a page exists for this specific error code, it will open in the default browser, or in the Help Viewer, if you installed and enabled offline help. With Visual Studio 17.12 and later, when you copy an error from the Error List using **Ctrl**+**C**, the description is copied to the clipboard. You can paste this into the browser to search for the error online, or share it with others. You can also copy the entire row by right-clicking the error and selecting **Copy Row** from the context menu or hitting **Ctrl**+**Shift**+**C**. To open the browser and initiate a search with Bing on the error description with one keystroke, press **Ctrl**+**F1**.
+
 ## Save
 
 You can copy the error list and save it to a file. Select the errors you want to copy and right-click the selection, then on the context menu select **Copy**. You can then paste the errors into a file. If you paste the errors to an Excel spreadsheet, the fields appear as different columns.
@@ -93,4 +97,4 @@ Displays the line where the problem occurs.
 
 **Details**
 
-Displays a clickable icon to open the [Problem Details window](../../ide/reference/problem-details-window.md) if this entry has additional details.
+Displays a clickable icon to open the [Problem Details window](../../ide/reference/problem-details-window.md) if this entry has additional details.
diff --git a/docs/ide/understanding-build-configurations.md b/docs/ide/understanding-build-configurations.md
@@ -1,7 +1,7 @@
 ---
 title: Understand build configurations
 description: Discover how to work with build configurations when you need to build your projects with different settings in Visual Studio.
-ms.date: 11/01/2023
+ms.date: 11/14/2024
 ms.subservice: compile-build
 ms.topic: conceptual
 f1_keywords:

diff --git a/docs/ide/walkthrough-building-an-application.md b/docs/ide/walkthrough-building-an-application.md
@@ -1,7 +1,7 @@
 ---
 title: 'Tutorial: Build an application'
 description: Become more familiar with several options that you can configure when you build applications with Visual Studio, such as hiding complier warnings.
-ms.date: 11/02/2023
+ms.date: 11/14/2024
 ms.subservice: compile-build
 ms.topic: tutorial
 author: ghogen

diff --git a/docs/msbuild/msbuild.md b/docs/msbuild/msbuild.md
@@ -1,7 +1,7 @@
 ---
 title: Use the MSBuild XML schema to control builds
 description: Explore how the Microsoft Build Engine (MSBuild) platform provides a project file with an XML schema to control builds with properties, items, tasks, and targets.
-ms.date: 11/03/2023
+ms.date: 11/14/2024
 ms.topic: overview
 helpviewer_keywords:
 - MSBuild, about MSBuild
@@ -15,7 +15,7 @@ ms.subservice: msbuild
 
 The Microsoft Build Engine is a platform for building applications. This engine, which is also known as MSBuild, provides an XML schema for a project file that controls how the build platform processes and builds software. Visual Studio uses MSBuild, but MSBuild doesn't depend on Visual Studio. By invoking *msbuild.exe* or *dotnet build* on your project or solution file, you can orchestrate and build products in environments where Visual Studio isn't installed.
 
-Visual Studio uses MSBuild to load and build managed projects. The project files in Visual Studio (*.csproj*, *.vbproj*, *.vcxproj*, and others) contain MSBuild XML code that executes when you build a project by using the IDE. Visual Studio projects import all the necessary settings and build processes to do typical development work, but you can extend or modify them from within Visual Studio or by using an XML editor.
+Visual Studio uses MSBuild to load and build managed projects. The project files in Visual Studio (*.csproj*, *.vbproj*, *.vcxproj*, and others) contain MSBuild XML code that executes when you build a project in the IDE. Visual Studio projects import all the necessary settings and build processes to do typical development work, but you can extend or modify them from within Visual Studio or by using a text editor.
 
 To install MSBuild on a Windows system that doesn't have Visual Studio, go to **Build Tools for Visual Studio** on the [downloads page](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-cta). Installing MSBuild by this method gives you *MSBuild.exe*.