Die Oberfläche von VDS Renaissance ist in mehreren Sprachen verfügbar. Die offizielle Dokumentation wird auf Englisch gepflegt, um eine einheitliche, konsistente und stets aktuelle Referenz zu gewährleisten.

Project Settings

The settings in this section are stored in the in the .DSP file which is created for each script. So any changes made do not have to be recreated the next time you create an executable from the same script.

Click on any are to learn what it does

Target specifies the name and location of the compiled file.

Target type specifies the type of file you want to build. The Visual DialogScript 7 compiler builds executables for the VDS 7 runtime, with a choice of types. Standard executables require the appropriate runtime DLL in order to run. Integrated executables can run standalone (but still require any extension DLLs that have been used.) You can also build console (command line) or NT service applications.

Icon specifies the icon to use for the compiled executable file. Note: You can change the default icon that is used by replacing the file default.ico, which is located into the Visual DialogScript main directory.

Include version information specifies whether you want to add version information to the compiled program. When this option is selected, the Version Info tab will appear, to allow the information to be entered.

Application manifest specifies whether you want to link a manifest into the executable file. A manifest is necessary for programs that will run under Windows XP, so that Windows XP will use the latest version of the common controls DLL which is XP theme-aware.

Under Windows Vista the manifest also specifies the Execution level required. This may be left as "<not specified>", but including execution level information indicates that the application has been developed with Windows Vista in mind. Normal applications should be run at the level of the user, "AsInvoker". Applications that require higher level privileges should use "Highest Available" or "Require Administrator".

[VDS7] Platform selects the target platform of the compiled program — Windows 32-bit, Windows 64-bit, or Linux. You can build any of these from either edition of the IDE; the IDE's own architecture no longer dictates the architecture of the program you build.

[VDS7] When Linux is selected, the Windows IDE produces a single-file Linux executable (ELF). The program is built as an integrated executable, with the runtime linked in, so it needs no separate runtime file on the target machine: the same one-file model as on Windows — build on Windows, run on Linux. (For a Linux target the output is the integrated executable only; resources, icon and version information follow the Windows build path.)

[VDS7] Sign output (Authenticode) signs the compiled executable with your certificate immediately after it is built. Configure the certificate once under Code signing (Options menu, or the Configure… button beside this checkbox). The signing tool's output is shown in the Compiler panel.

Create map file

specifies that a map listing is to be produced

when the program is compiled. This listing shows the line numbers of all

labels and the names of global variables used. It is useful when trying to understand run-time error messages and trace listings.

Unit projects

Not all projects result in the creation of a program that can run stand-alone. A project target may be a DialogScript unit (.dsu) file. Units are a convenient way to distribute tested sections of code intended for inclusion in other scripts.