|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
Application Page, Project Designer (Visual Basic)
Use the Application page of the Project Designer to specify the project's application settings and properties.
To access the Application page, select a project node in Solution Explorer, then on the Project menu, click Properties. When the Project Designer appears, click the Application tab.
General Application Settings
The following options enable you to configure general settings for the application.
- Assembly name
Specifies the name of the output file that will hold the assembly manifest. Changing this property will also change the Output Name property. You can also make this change from the command line using. To access this property programmatically, see .
- Root namespace
Specifies the base namespace for all files in the project. For example, if you set the root namespace to Project1 and you have a Class1 outside of any namespace in your code, its namespace would be Project1.Class1. If you have a Class2 within a namespace Order in code, its namespace would be Project1.Order.Class2.
It is also possible to clear the root namespace property, which allows you to manually specify the namespace structure of your project. Seefor more information on creating namespaces in your code.
Seefor more information. To access this property programmatically, see .
- Application type
Specifies the type of application to build. In a Web Application project, this property can only be set to Class Library. Seefor more information. To access this property programmatically, see .
Sets the .ico file that you want to use as your application icon. Select <Browse...> to browse for an existing graphic. See(or ) for more information. To access this property programmatically, see .
- Startup form / Startup object
Specifies the application's startup form or entry point.
If Enable application framework is selected (the default), this list is Startup form, and shows only forms because the application framework only supports startup forms, not objects.
If Enable application framework is cleared, this list becomes Startup object and shows both forms and classes or modules with a Sub Main.
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. To access this property programmatically, see .
- Assembly Information
For more information, see.
- Enable application framework
Specifies whether or not a project will use the application framework. The setting of this option affects the options available in Startup form/Startup object.
If this check box is selected, your application uses the standard Sub Main, which enables the features in the Windows application framework properties section, and also requires you to select a startup form.
If this check box is cleared, your application uses the custom Sub Main that you specified in Startup form. In this case you can specify either a start-up object (a custom Sub Main in a method or a class) or a form. Also, the options in the Windows application framework properties section are unavailable.
Windows Application Framework Properties
The following settings are used to configure the Windows application framework properties section. These options are only available if the Enable application framework check box is selected.
- Enable XP visual styles
Enable or disable the Windows XP visual styles, also known as Windows XP Themes. Windows XP visual styles allow, for example, controls with rounded corners and dynamic colors. The default is enabled. For more information on using this setting, see. For more information on Windows XP visual styles, see and .
- Make single instance application
Select this check box to prevent users from running multiple instances of your application. The default setting for this check box is cleared, allowing multiple instances of the application to be run. For more information, see.
- Save My.Settings on Shutdown
Selecting this check box specifies that the application's My.Settings settings be saved on shutdown. The default setting is enabled. If this option is disabled, you can do this manually by calling My.Settings.Save.
- Authentication mode
Select Windows (the default) to specify the use of Windows authentication to identify the currently logged-on user. This information can be retrieved at run time using the My.User object. Select Application-defined if you will provide your own code to authenticate users rather than using the default Windows authentication methods. For more information on using this setting, see.
- Shutdown mode
Select When startup form closes (the default) to specify that the application end when the form set as the Startup form closes, even if other forms are open. Select When last form closes to specify that the application end when the last form is closed or when My.Application.Exit or the End statement is called explicitly. For more information on using this setting, see.
- Splash screen
Select the form that you want to use as a splash screen. You must have previously created a splash screen using a form or a template, as described in. The default is (None).
- View Application Events
Clicking this button displays an events code file, in which you can write events against the application framework events (Startup, Shutdown, UnhandledException, StartupNextInstance and NetworkAvailabilityChanged). You can also override certain application framework methods, for example, changing the display behavior of the splash screen by overriding OnInitialize.