Navigation:  Commands and Procedures >

Configuration Files

Previous pageReturn to chapter overviewNext page

Visual Build (both the GUI and Console apps) utilizes the following configuration files for global application settings and user action files:


VisBuildPro.config: Application options
VisBuildPro.macros: Global macros
VisBuildPro.Global.scripts: Global scripts
VisBuildPro.steps: Global subroutine steps


The File Locations dialog displays the current location of the config files being used.  The default path used for the configuration files is determined at startup as follows:


First, if the /configpath GUI or console command-line switch is specified, that path will be used for loading and saving the configuration files.
Next, if the REG_SZ registry value HKEY_LOCAL_MACHINE\SOFTWARE\Kinook Software\Visual Build Professional 9\ConfigFilesPath exists, the path in that value will be used for loading and saving the configuration files.
If neither of the above exist, the configuration files will be loaded and saved in the Windows common Application Data folder (located at %ALLUSERSPROFILE%\Application Data\Kinook Software\Visual Build Professional 9 -- usually C:\Documents and Settings\All Users\Application Data\Kinook Software\Visual Build Professional 9 on Windows 2003 or C:\ProgramData\Kinook Software\Visual Build Professional 9 on Windows Vista and later).


Two additional methods are provided for explicitly specifying where configuration files are loaded from and/or saved to:


The location of each individual configuration file can be overridden by supplying additional command-line flags when launching the Visual Build GUI or Console apps.
Configuration files can be explicitly loaded from a Run Script step in a build using the Object Model:


Application options => Application.Options.Load "drive:path\to\filename.ext"

Global macros => Application.Macros(vbldMacroGlobal).Load "drive:path\to\filename.ext", True

Global scripts => Application.Scripts(vbldScriptGlobal).Load "drive:path\to\filename.ext"

Global subroutine steps => Application.Project.Steps(vbldStepGlobalSubroutine).Load "drive:path\to\filename.ext"