VDS Renaissance のインターフェースは複数の言語に対応しています。公式ドキュメントは、単一で一貫した常に最新のリファレンスを保証するため、英語で管理されています。

Development Environment

Visual DialogScript has an interactive development environment (IDE) which makes it easy to develop and debug your Windows scripts.

For a description of each feature of the IDE interface, click on a button or menu or area on the picture below.

The debugger has dockable toolbars and tear-off editor and information window panes. The editor has support for mouse-wheel scrolling and drag-and-drop editing.

The VDS development is project-based. The main file that you open is the project (.DSP) file, which contains important settings for the project. The project manager allow you to change some of these settings.

The script file (.DSC) of the same name as the project is the main (and in many cases only) file of the project. However, in VDS 5 a program can contain code from multiple .DSC files (by means of the #INCLUDE command). To permit the development of multi-file projects the IDE supports multiple editor panes.

When creating a new file, the IDE can use a predefined template. Just create a file in the format required and save it as 'default.dsc' in the same folder as VDS.EXE. When a script file is saved, the previous version is renamed with a .~dsc extension, similar to before. However, the previous .~dsc file is deleted to the Recycle Bin. Therefore you can use your Recycle Bin to restore any previous version of a script even after several modifications have been saved.

Scripts are edited in the script area, which is an advanced multi tabbed text editor with syntax highlighting. Scripts can be run from the main window, using either the menu options or the toolbar buttons.

[VDS7] Find and Replace can search across all open files (a checkbox in both dialogs), and the list of search and replace terms is remembered per project.

Visual DialogScript provides several aids to debugging. You can set breakpoints at any point in the script throught the script window, and then check the value of each variable using the debug window. You can also use single-step mode to step through the script a line at a time.

[VDS7] Editions and files. The IDE ships in two editions, vds32.exe (32-bit) and vds64.exe (64-bit) — replacing the single vds.exe of earlier versions. Either edition can build programs for either architecture (see Platform). A standalone compiled program needs the matching runtime DLL beside it, vds32run70.dll or vds64run70.dll; integrated programs need no runtime DLL. The IDE keeps its own settings in vdside.ini, in the program folder, rather than in the registry.

The Options menu lets you set your preferences for various options in the development environment.

The Tools menu provides access to tools which you may find helpful when creating your script program. You can add your own tools to the menu. Check our Web site for add-in tools you can download.

[VDS7] The IDE title bar shows the edition being run (for example "VDS Renaissance - 64 bits"). The Tip of the Day shown at start-up can be opened any time from Tools - Tip of the Day, and turned off from there.

[VDS7] Interface languages. The Language menu offers, in addition to English, French, Spanish, German and Dutch, Simplified Chinese (简体中文) and Japanese (日本語). The interface (menus, toolbars, dialogs and messages) is fully translated. Language files are plain key=value files named <code>.lng in the lang folder, and are discovered automatically at start-up: dropping a new <code>.lng beside the program adds that language without recompiling, and it takes priority over the built-in version. The files are read as UTF-8, so a language file may contain any script (CJK, Cyrillic, accents). To add a language, copy en.lng, translate the values, and save it as <code>.lng (UTF-8) in the lang folder.