kinook
04-08-2003, 08:41 AM
Visual Build Pro (both the GUI and Console apps) utilizes the following configuration files for global application settings and user action files:
<li>VisBuildPro.config: Application options
<li>VisBuildPro.macros: Global macros
<li>VisBuildPro.Global.scripts: Global scripts
<li>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:
<li>First, if the /configpath GUI or console command-line switch is specified, that path will be used for loading and saving the configuration files.
<li>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.
<li>Next, if any of the configuration files exist in the Visual Build Pro installation directory, they will be loaded from and saved to that location.
<li>Finally, if neither of the above exist, the configuration files will be loaded and saved at the Windows common Application Data folder (located at C:\Documents and Settings\All Users\Application Data\Kinook Software\Visual Build Professional 9 [%ALLUSERSPROFILE% can also be used for the root path]).
Two additional methods are provided for explicitly specifying where the configuration files are loaded from and/or saved to:
<li>The location of each configuration file can be overridden by supplying additional command-line flags when launching the Visual Build Pro GUI or Console apps (see http://visualbuild.com/Manual/?command_linegui.htm and http://visualbuild.com/Manual/?consoleapp.htm).
<li>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"
<li>VisBuildPro.config: Application options
<li>VisBuildPro.macros: Global macros
<li>VisBuildPro.Global.scripts: Global scripts
<li>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:
<li>First, if the /configpath GUI or console command-line switch is specified, that path will be used for loading and saving the configuration files.
<li>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.
<li>Next, if any of the configuration files exist in the Visual Build Pro installation directory, they will be loaded from and saved to that location.
<li>Finally, if neither of the above exist, the configuration files will be loaded and saved at the Windows common Application Data folder (located at C:\Documents and Settings\All Users\Application Data\Kinook Software\Visual Build Professional 9 [%ALLUSERSPROFILE% can also be used for the root path]).
Two additional methods are provided for explicitly specifying where the configuration files are loaded from and/or saved to:
<li>The location of each configuration file can be overridden by supplying additional command-line flags when launching the Visual Build Pro GUI or Console apps (see http://visualbuild.com/Manual/?command_linegui.htm and http://visualbuild.com/Manual/?consoleapp.htm).
<li>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"