Additional Ways to Start Builds

Starting a Build from the Tray Icon Menu

If IncrediBuild's installation was successfully completed on your machine, you will notice the IncrediBuild tray-icon display in the lower right-hand part of your screen.
When holding your mouse pointer directly above the icon, a tooltip should appear with the words "IncrediBuild Agent (Enabled)". If some other tooltip text appears, or if the IncrediBuild Agent tray-icon display is missing, see the troubleshooting section in the F.A.Q page.

Right-click the IncrediBuild Agent tray-icon display to display the Agent menu. Choose Build and then Open... from the sub-menu. Next, browse to the location of the project (.vcproj/.dsp), solution (.sln) or workspace (.dsw) file to be built, and click the Open button. The Batch Build dialog will open, listing the different project/solution configurations available:

Select one or more configurations to build by clicking on the checkboxes to the left of the configuration names. Next, click either Build (to only build files that are out of date) or Rebuild (to delete the intermediate and output files before starting a new build).

The Build Monitor should open, displaying the build's progress. To learn more about this display, click here.

Starting a Build from the Command Line

Builds can also be initiated from the command line and from batch scripts. To start a build, type the following from the command line:
BuildConsole <targetfile>
Where <targetfile> is the path to a project (.DSP or .VCProj file), solution (.SLN file) or workspace (.DSW file).

Additional options such as /rebuild (to rebuild the project), /prj="..." (to specify the project to be built from a target solution/workspace) and /cfg="..." (to specify the target configuration) are available. For a full list of these options and a brief explanation, run BuildConsole from the command line with no input parameters.

For a full reference of BuildConsole's features, click here.

Copyright (C) 2001-2008 Xoreax Software Ltd. All rights reserved.
Converted from CHM to HTML with chm2web Standard 2.7 (unicode)