Project Options (Application)

This is a IDE topic about Oxygene
 

Code Editor | Visual Designers | Build Toolchain | Debugging | Project Management | Templates

Application Option	Description	Default Value
Assembly Name	The name of the assembly (excluding the extension) that will be generated when building the project. It is common (though not required) for this name to match the project name.	By default, this is the file name of the project, without the extension.
Default Namespace	Specifies the namespace for all subsequent source files. It defaults to the Assembly Name. This namespace might also be used by third party tools that generate code for your projects.	By default this is the file name of the project, without the extension.
Internal Assembly Name	Internal name for the assembly generated when building the project. It is very rare that you will want to use a different internal name for the assembly than the filename, so by default this option is empty and the same name will be used for both. If set, this option affects the Strong Name of the generated assembly.	By default, this option is empty, so the Assembly Name is used as the internal name.
Startup Object	For Exe and WinExe project types, a static Main method ("method Main(args: array of string): integer;") must be implemented by one class to be used as entry point for the application. If only one such Main method exists, the Oxygene compiler will automatically find it and use it as the entry point; if however multiple classes provide a Main method, this option can be set to select which class to use.	By default, this is empty, so the compiler will try to find this method on its own.
Target Framework	Specifies the version of the .NET Framework (or its profile) that the current project targets. This option can have different available values depending on which versions of the .NET Framework are available on the host computer.	The default value depends on the chosen project type, for example for a Silverlight application, it will be Silverlight.
Output Type	Available Options are: Executable Library Windows Executable Libraries are .dll projects without entry points, while Executables and Windows Executables are .exe projects that contain an entry point. An Executable project will run as a console application (and open a new console window when run outside of a console), while Windows Executables run without a console.	The default value depends on the chosen project type, for example for class libraries, it will be Library. For console applications, it will be Executable and for most others, it will be Windows Executable.
Default Uses	Projects often require the same set of namespace references for each new source file. Specifying the name(s) here, separated by semi-colons, is an easier alternative. See the uses statement for more details.	By default, this field is empty.
Application Icon	The .ico file is used as the application icon for executable files. The icon file specified here will be linked into the .exe file as a Win32 resource and shown in Windows Explorer. This icon does not affect the runtime behavior of the application or the icon of the main form.	For most applications, this is set to Properties\App.ico, which is the application icon part of the template.

See Also

• Project Options
  • Application – Compatibility – Build – Build Events – Reference Paths – Debug – Signing – Resources – Settings
  • Specialised property pages: MacPack
• IDE Integration