Navigation:  Introduction >


Previous pageReturn to chapter overviewNext page

System Requirements


Visual Build runs on Microsoft Windows 7 thru Windows 11 and Server 2003 thru Server 2022 (32- and 64-bit editions).
Installation must be performed by an account with admin privileges.
About 35 MB free disk space.
256-color and 800 x 600 resolution display settings (Recommended: 16-bit color and 1024 x 768 resolution or greater).


Note: Visual Build is available in 32-bit and 64-bit editions (via separate downloads).  The 32-bit edition is compatible with 32-bit editions of Windows as well as 64-bit editions of Windows with the WoW64 subsystem (which is installed with most flavors of Windows but is optional on Windows Server 2008 R2 Server Core and later).  The 64-bit edition is a native x64 executable that does not use the WoW64 subsystem and must be installed on a 64-bit edition of Windows.


Installation Procedure


1.Run the setup application (VisBuildProEval.exe or VisBuildProX64Eval.exe for the 64-bit edition).
2.Follow the instructions on the installation dialogs.  Please note that the software can only be installed for the number of computers or users it has been licensed for.  Multiple and site licenses are available.  Visit the Kinook Software web site for more information.
3.Once Visual Build has been successfully installed, you will find new start menu icons for Visual Build.  Entries for the application, help, and samples will be available.


Build-Only Installation


If the Minimal installation option is chosen, only the console application (not the GUI app or any start menu shortcuts) and required build components will be installed.  This can be useful for providing a read-only/build-only installation of Visual Build, since no GUI for editing project files will be available.  However, a license is still required and the license must be registered (see below).


Unattended Installation and Registration


The Visual Build installer accepts the following optional command line parameters:



The wizard and background window are not displayed but the installation progress window is. When a setup is very silent, the progress window is not displayed. Error messages during installation are displayed.  If a restart is necessary and the /NORESTART command isn't used and Setup is silent, it will display a Reboot now? message box. If it's very silent, it will reboot without asking.


Suppresses messageboxes. Only has an effect when combined with /SILENT and /VERYSILENT.

The default response in situations where there's a choice is:

-Yes in a 'Keep newer file?' situation.

-No in a 'File exists, confirm overwrite.' situation.

-Abort in Abort/Retry situations.

-Cancel in Retry/Cancel situations.

-Yes (=continue) in a DiskSpaceWarning/DirExists/DirDoesntExist/NoUninstallWarning/ExitSetupMessage/ConfirmUninstall


-Yes (=restart) in a FinishedRestartMessage/UninstalledAndNeedsRestart situation.


Creates a log file in the user's TEMP directory detailing file installation and [Run] actions taken during the installation process. This can be a helpful debugging aid. For example, if you suspect a file isn't being replaced when you believe it should be (or vice versa), the log file will tell you if the file was really skipped, and why.  The log file is created with a unique name based on the current date. (It will not overwrite or append to existing files.)  The information contained in the log file is technical in nature and therefore not intended to be understandable by end users. Nor is it designed to be machine-parseable; the format of the file is subject to change without notice.


Same as /LOG, except it allows specifying a fixed path/filename to use for the log file. If a file with the specified name already exists it will be overwritten. If the file cannot be created, Setup will abort with an error message.


Prevents cancelling the installation process by disabling the Cancel button and ignoring clicks on the close button. Useful along with /SILENT or /VERYSILENT.


Does not reboot even if necessary.


Overrides the default directory name displayed on the Select Destination Location wizard page. A fully qualified pathname must be specified.

/GROUP="folder name"

Overrides the default folder name displayed on the Select Start Menu Folder wizard page.


Initially checks the Don't create any icons checkbox on the Select Start Menu Folder wizard page.


Specifies a setup type for the Select Components wizard page (full, compact, or minimal).

/COMPONENTS="comma separated list of component names"

Specifies components for the Select Components wizard page (required, application, samples, addins, and/or tools), selecting a custom installation type.  Only the specified components will be selected; the rest will be unchecked.  If a component name is prefixed with a "!" character, the component will be unchecked.

/TASKS="comma separated list of task names"

Specifies a list of tasks from the Select Additional Tasks wizard page (desktopicon, quicklaunchicon, assoc, and/or explorer) that should be selected.  Only the specified tasks will be checked; the rest will be unchecked. If a task name is prefixed with a "!" character, the task will be unchecked.


Automated entry of license info requires using the object model, either within Visual Build via the vbld_BuildStarting script event (VBScript) like:


Builder.RegisterKey "name + license count", "license key"


or outside Visual Build (i.e., in a .vbs file):


Set bld = CreateObject("VisBuildSvr.Builder")

bld.RegisterKey "name + license count", "license key"


Alternatively, run Visual Build as administrator and register, or create a text file named C:\Program Files\VisBuildPro10\System\VisBuildSvr.ini (in the Visual Build installation System subfolder) with contents like:



PortableKey=license name + count,license key


Note: Replace "name + license count" and "license key" above with the actual license name + count and key from your license info email.