The following options enable you to configure general settings for an application.
- Assembly name
Specifies the name of the output file that will contain the assembly manifest. If you change this property, the Output Name property will also change. You can also make this change at a command prompt by using /out (Visual Basic). For information about how to access this property programmatically, see AssemblyName.
- 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 in a namespace Order in code, its namespace would be Project1.Order.Class2.
It is also possible to clear the root namespace property, which enables you to specify the namespace structure of your project manually.
For information about how to create namespaces in your code, see Namespace Statement.
For more information about the root namespace property, see /rootnamespace.
For information about how to access this property programmatically, see RootNamespace.
- Application type
Specifies the type of application to create. In a Web Application project, this property can be set only to Class Library. For more information, see /target. For information about how to access this property programmatically, see OutputType.
Sets the .ico file that you want to use as your program icon. Select <Browse...> to browse for an existing graphic. See /win32icon (or /win32icon (Import an .ico File) (C# Compiler Options)) for more information. To access this property programmatically, see ApplicationIcon.
- Startup form / Startup object / Startup URI
Specifies the application's startup form or entry point.
If Enable application framework is selected (the default), this list is titled Startup form and shows only forms because the application framework supports only startup forms, not objects.
If the project is a WPF Browser Application, this list is titled Startup URI, and the default is Page1.xaml. The Startup URI list enables you to specify the user interface resource (a XAML element) that the application displays when the application starts. For more information, see StartupUri.
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 /main. To access this property programmatically, see StartupObject.
- Assembly Information
Click this button to display the Assembly Information Dialog Box.
- Enable application framework
Specifies whether 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. Selecting this check box 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 startup object (a custom Sub Main in a method or a class) or a form. Also, the options in the Windows application framework properties section become unavailable.
- View UAC Settings
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:
<requestedExecutionLevel level="asInvoker" />
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.
For more information about manifest generation, see ClickOnce Deployment on Windows Vista.