You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/deployment/installer-projects-net-core.md
+14-7Lines changed: 14 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "Visual Studio Installer Projects and .NET"
3
3
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).
4
4
titleSuffix: ""
5
-
ms.date: "03/13/2024"
5
+
ms.date: "11/13/2024"
6
6
ms.topic: "conceptual"
7
7
helpviewer_keywords:
8
8
- "installer projects"
@@ -17,7 +17,7 @@ monikerRange: '>= vs-2019'
17
17
18
18
Packaging applications as an MSI is often accomplished using the Visual Studio Installer Projects Extension.
19
19
20
-
This article applies to apps targeting .NET Core 3.1, .NET 5, .NET 6, and later.
20
+
This article applies to apps targeting .NET Core 3.1 and .NET 5 or later versions.
21
21
22
22
You can download the extension here:
23
23
@@ -52,13 +52,20 @@ To learn more about these deployment strategies, see [.NET application publishin
52
52
53
53
### Workflow changes for .NET Core 3.1 and .NET 5 or later
54
54
55
-
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.
55
+
- 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.
56
56
57
-

57
+

58
58
59
-
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.
59
+
- 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.
60
60
61
-

61
+
::: moniker range=">= vs-2022"
62
+
:::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":::
63
+
::: moniker-end
64
+
::: moniker range="vs-2019"
65
+

66
+
::: moniker-end
67
+
68
+
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.
62
69
63
70
>[!NOTE]
64
71
>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
69
76
70
77

71
78
72
-
The **.NET Core Runtime...** option should be selected for console applications, **.NET Desktop Runtime...** should be selected for WPF/WinForms applications.
79
+
The **.NET Core Runtime...** option should be selected for console applications, **.NET Desktop Runtime...** should be selected for WPF and WinForms applications.
73
80
74
81
>[!NOTE]
75
82
>These items are present starting with the Visual Studio 2019 Update 7 release.
0 commit comments