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/ide/reference/application-page-project-designer-visual-basic.md
+28-20Lines changed: 28 additions & 20 deletions
Original file line number
Diff line number
Diff line change
@@ -20,17 +20,21 @@ ms.workload:
20
20
21
21
Use the **Application** page of the Project Designer to specify a project's application settings and properties.
22
22
23
-
To access the **Application** page, choose a project node (not the **Solution** node) in **Solution Explorer**. Then choose **Project** > **Properties** on the menu bar. When the Project Designer appears, select the **Application** tab.
23
+
To access the **Application** page, choose a project node (not the **Solution** node) in **Solution Explorer**. Then choose **Project** > **Properties** on the menu bar. When the **Project Designer** appears, select the **Application** tab.
The following options enable you to configure general settings for an application.
30
30
31
31
### Assembly name
32
32
33
-
Specifies the name of the output file that will contain the assembly manifest. If you change this property, the **Output Name** property also changes. You can also specify the name of the output file from a command prompt by using the [/out (Visual Basic)](/dotnet/visual-basic/reference/command-line-compiler/out) compiler switch. For information about how to access this property programmatically, see <xref:VSLangProj.ProjectProperties.AssemblyName%2A>.
33
+
Specifies the name of the output file that will contain the assembly manifest. If you change this property, the **Output Name** property also changes.
34
+
35
+
You can also specify the name of the output file from a command prompt by using the [/out (Visual Basic)](/dotnet/visual-basic/reference/command-line-compiler/out) compiler switch.
36
+
37
+
For information about how to access this property programmatically, see <xref:VSLangProj.ProjectProperties.AssemblyName%2A>.
34
38
35
39
### Root namespace
36
40
@@ -39,7 +43,7 @@ Specifies the base namespace for all files in the project. For example, if you s
39
43
If you clear the **Root Namespace**, you can specify the namespace structure of your project in code.
40
44
41
45
> [!NOTE]
42
-
> If you use the Global keyword in a [Namespace Statement](/dotnet/visual-basic/language-reference/statements/namespace-statement), you can define a namespace out of the root namespace of your project. If you clear the **Root Namespace**, `Global` becomes the top-level namespace, which removes the need for the `Global` keyword in a `Namespace` statement. For more information, see "Global Keyword in Namespace Statements" in [Namespaces in Visual Basic](/dotnet/visual-basic/programming-guide/program-structure/namespaces).
46
+
> If you use the `Global` keyword in a [Namespace Statement](/dotnet/visual-basic/language-reference/statements/namespace-statement), you can define a namespace out of the root namespace of your project. If you clear the **Root Namespace**, `Global` becomes the top-level namespace, which removes the need for the `Global` keyword in a `Namespace` statement. For more information, see "Global Keyword in Namespace Statements" in [Namespaces in Visual Basic](/dotnet/visual-basic/programming-guide/program-structure/namespaces).
43
47
44
48
For information about how to create namespaces in your code, see [Namespace Statement](/dotnet/visual-basic/language-reference/statements/namespace-statement).
45
49
@@ -60,20 +64,17 @@ For more information, see [How to: Target a Version of the .NET Framework](../..
60
64
61
65
### Application type
62
66
63
-
Specifies the type of application to build. For Windows 8.x apps, you can specify **Windows Store App**, **Class Library**, or **WinMD File**. For most other application types, you can specify **Windows Application**, **Console Application**, **Class Library**, **Windows Service**, or **Web Control Library**.
67
+
Specifies the type of application to build. The values are different depending on the project type. For example, for a **Windows Forms App** project, you can specify **Windows Forms Application**, **Class Library**, **Console Application**, **Windows Service**, or **Web Control Library**.
64
68
65
69
For a web application project, you must specify **Class Library**.
66
70
67
-
If you specify the **WinMD File** option, types can be projected into any Windows Runtime programming language. By packaging the project's output as a WinMD file, you can code an application in multiple languages and have code interoperate as if you wrote it all in the same language. You can use the **WinMD File** option for solutions that target the Windows Runtime libraries, including [!INCLUDE[win8_appname_long](../../debugger/includes/win8_appname_long_md.md)] apps. For more information, see [Creating Windows Runtime Components in C# and Visual Basic](/windows/uwp/winrt-components/creating-windows-runtime-components-in-csharp-and-visual-basic).
68
-
69
-
> [!NOTE]
70
-
> The Windows Runtime can project types so that they appear as native objects in whichever language uses them. For example, JavaScript applications that interact with Windows Runtime use it as a set of JavaScript objects, and C# applications use the library as a collection of .NET objects. By packaging the project's output as a WinMD file, you can take advantage of the same technology that Windows Runtime uses.
71
-
72
71
For more information about the **Application type** property, see [/target (Visual Basic)](/dotnet/visual-basic/reference/command-line-compiler/target). For information about how to access that property programmatically, see <xref:VSLangProj.ProjectProperties.OutputType%2A>.
73
72
74
-
### Icon
73
+
### Auto-generate binding redirects
75
74
76
-
Sets the .ico file that you want to use as your program icon. Select **\<Browse...>** to browse for an existing graphic. See [/win32icon](/dotnet/visual-basic/reference/command-line-compiler/win32icon) (or [/win32icon (C# Compiler Options)](/dotnet/csharp/language-reference/compiler-options/win32icon-compiler-option)) for more information. To access this property programmatically, see <xref:VSLangProj.ProjectProperties.ApplicationIcon%2A>.
75
+
Binding redirects are added to your project if your app or its components reference more than one version of the same assembly. If you want to manually define binding redirects in the project file, deselect **Auto-generate binding redirects**. This checkbox was introduced in Visual Studio 2017 version 15.7.
76
+
77
+
For more information about redirection, see [Redirecting assembly versions](/dotnet/framework/configure-apps/redirect-assembly-versions).
77
78
78
79
### Startup form / Startup object / Startup URI
79
80
@@ -87,6 +88,10 @@ If **Enable application framework** is cleared, this list becomes **Startup obje
87
88
88
89
**Startup object** defines the entry point to be called when the application loads. Generally this is set to either the main form in your application or to the `Sub Main` procedure that should run when the application starts. Because class libraries do not have an entry point, their only option for this property is **(None)**. For more information, see [/main](/dotnet/visual-basic/reference/command-line-compiler/main). To access this property programmatically, see <xref:VSLangProj.ProjectProperties.StartupObject%2A>.
89
90
91
+
### Icon
92
+
93
+
Sets the .ico file that you want to use as your program icon. Select **\<Browse...>** to browse for an existing graphic. See [/win32icon](/dotnet/visual-basic/reference/command-line-compiler/win32icon) (or [/win32icon (C# Compiler Options)](/dotnet/csharp/language-reference/compiler-options/win32icon-compiler-option)) for more information. To access this property programmatically, see <xref:VSLangProj.ProjectProperties.ApplicationIcon%2A>.
94
+
90
95
### Assembly Information
91
96
92
97
Click this button to display the [Assembly Information Dialog Box](../../ide/reference/assembly-information-dialog-box.md).
@@ -101,17 +106,20 @@ If this check box is cleared, your application uses the custom `Sub Main` that y
101
106
102
107
### View Windows Settings
103
108
104
-
Click this button to generate and open the app.manifest file. Visual Studio uses this file to generate manifest data for the application. Then set the UAC requested execution level by modifying the `<requestedExecutionLevel>` tag in app.manifest as follows:
109
+
Click this button to generate and open the *app.manifest* file. Visual Studio uses this file to generate manifest data for the application. Then set the UAC requested execution level by modifying the `<requestedExecutionLevel>` tag in *app.manifest* as follows:
105
110
106
111
`<requestedExecutionLevel level="asInvoker" />`
107
112
108
113
ClickOnce works with a level of `asInvoker` or in virtualized mode (no manifest generation). To specify virtualized mode, remove the entire tag from app.manifest.
109
114
110
115
For more information about manifest generation, see [ClickOnce Deployment on Windows Vista](../../deployment/clickonce-deployment-on-windows-vista.md).
111
116
112
-
## Windows Application Framework Properties
117
+
## Windows application framework properties
118
+
119
+
The following settings are available in the **Windows application framework properties** section. These options are available only if the **Enable application framework** check box is selected.
113
120
114
-
The following settings are available in the **Windows application framework properties** section. These options are available only if the **Enable application framework** check box is selected. The section following this one describes **Windows application framework properties** settings for Windows Presentation Foundation (WPF) Applications.
121
+
> [!TIP]
122
+
> The section following this one describes **Windows application framework properties** settings specific to Windows Presentation Foundation (WPF) apps.
115
123
116
124
### Enable XP visual styles
117
125
@@ -147,13 +155,13 @@ Select the form that you want to use as a splash screen. You must have previousl
147
155
148
156
Click this button to display an events code file in which you can write events for the application framework events `Startup`, `Shutdown`, `UnhandledException`, `StartupNextInstance` and `NetworkAvailabilityChanged`. You can also override certain application framework methods. For example, you can change the display behavior of the splash screen by overriding `OnInitialize`.
149
157
150
-
## Windows Application Framework Properties for Windows Presentation Foundation (WPF) Applications
158
+
## Windows application framework properties for Windows Presentation Foundation (WPF) apps
151
159
152
-
The following settings are available in the **Windows application framework properties** section when the project is a Windows Presentation Foundation application. These options are available only if the **Enable application framework** check box is selected. The options listed in this table are available only for WPF applications or WPF browser applications. They are not available for WPF User Control or Custom Control libraries.
160
+
The following settings are available in the **Windows application framework properties** section when the project is a Windows Presentation Foundation (WPF) app. These options are available only if the **Enable application framework** check box is selected. The options listed in this table are available only for WPF or WPF browser applications. They are not available for WPF User Control or Custom Control libraries.
153
161
154
162
### Shutdown mode
155
163
156
-
This property is applicable only to Windows Presentation Foundation applications.
164
+
This property is applicable only to Windows Presentation Foundation (WPF) applications.
157
165
158
166
Select **On explicit shutdown** to specify that the application exit when you explicitly call <xref:System.Windows.Application.Shutdown%2A>.
159
167
@@ -165,10 +173,10 @@ For more information about using this setting, see <xref:System.Windows.Applicat
165
173
166
174
### Edit XAML
167
175
168
-
Click this button to open and modify the application definition file (Application.xaml) in the XAML editor. When you click this button, Application.xaml opens at the application definition node. You might have to edit this file to perform certain tasks, such as defining resources. If the application definition file does not exist, the Project Designer creates one.
176
+
This button opens the application definition file (Application.xaml) in the XAML editor. When you click this button, *Application.xaml* opens at the application definition node. You might have to edit this file to perform certain tasks, such as defining resources. If the application definition file does not exist, the Project Designer creates one.
169
177
170
178
### View Application Events
171
179
172
-
Click this button to display the `Application`partial class file (Application.xaml.vb) in a code editor. If the file does not exist, the Project Designer creates one with the appropriate class name and namespace.
180
+
This button opens the `Application` class file (*Application.xaml.vb*) in a code editor. If the file does not exist, the Project Designer creates one with the appropriate class name and namespace.
173
181
174
182
The <xref:System.Windows.Application> object raises events when certain application state changes occur (for example, on application startup or shutdown). For a full list of the events that this class exposes, see <xref:System.Windows.Application>. These events are handled in the user code section of the `Application` partial class.
0 commit comments