Running Visual Studio in the Command Line

Use this option when the command line for running BuildConsole is too long to specify explicitly in your script.

By default, Incredibuild stops the build when a project fails to build its output file. This option instructs Incredibuild to continue building the remaining project configurations, regardless of previous projects failing to build.

If a build is currently running on the machine, this displays the output for the build up to that point, and continues displaying the build's output until it ends. If no build is running, BuildConsole displays the entire build output for the last build initiated from this machine.

A value (either ON or OFF) is mandatory.

See Agent Settings for more information regarding browse information settings.

For VS 2008 and prior.

• The value should be enclosed in quotes.

• Several comma-separated configuration names can be specified.

• When building an MSVC 6.0 project, both the following formats are valid: /cfg="Win32 Debug" and /cfg="myProj - Win32 Debug".

• The value is not case-sensitive.

Enter one or more commands separated by a space character, as they would appear in the cl.exe command line.

For example: BuildConsole MyProj /cl_add="/O2 /FA"

Enter one or more commands separated by a space character, as they would appear in the cl.exe command line.

For example: BuildConsole MyProj /cl_rem="/Z7 /Zd /Zi /ZI"

• Value may be surrounded by quotes.

• Several source filenames may be entered, separated by commas.

Only relevant for Visual Studio 2010 builds.

<output filename> is mandatory.

For VS 2008 and prior.

For VS 2008 and prior.

For example: /IntelCLVersion=11.1

Enter one or more commands separated by a space character, as they would appear in the cl.exe command line.

For example: BuildConsole MyProj /link_add="/map:MyProj.map"

For VS 2008 and prior.

Enter one or more commands separated by a space character, as they would appear in the cl.exe command line.

For example: BuildConsole MyProj /link_rem="/map:MyProj.map"

If filename is omitted, a file named IB_<target-name>.log is created in the current directory.

<Level> can be one of the following: Minimal, Basic, Intermediate, Extended, Detailed.

Agents with a newer OS are not assigned to the build. Available values are: XP, 2003, VISTA, 2008, 7, and 10.

Agents with an older OS are not assigned to the build. Available values are: XP, 2003, VISTA, 2008, 7, 8, and 10.

• If only a folder name is given, Incredibuild generates a GUID for the file name. 

• A message containing the location of the saved .ib_mon file is added to the end of the build output.

For example:

BuildConsole dcom.sln /rebuild /cfg="debug|win32" /msbuildargs="/detailedsummary" /usemsbuild

When this switch is specified in the command line, it instructs Incredibuild not to virtualize the .NET environment of the Initiator machine to the Helper machines. This switch was added to address .NET incompatibilities in a mixed OS environment.

For VS 2008 and prior.

For VS 2008 and prior.

• When used in conjunction with /Clean, this cleans only the specified configurations.

• When used in conjunction with /Rebuild, this rebuilds only the specified configurations.

/pemode=0 disables predictive execution

/pemode=2 fully enables predictive execution

/pemode=1 enables predictive execution for rebuilds only

• This option is useful when a complex combination of projects and configurations is required.

• The /Preset command option replaces both the /cfg and the /prj options.

• The value may be enclosed in quotes.

• Running BuildConsole on an .sln file without the /prj option will run the command on the specified solution configuration.

• The "*" and "?" characters may be used as wildcard signs when specifying project names, to perform an operation on several projects.

• Additionally, several project names may be entered, separated by commas. In this case, all projects are built using the same configuration name.

• For example, to build all configurations in a solution/workspace, use the following syntax: BuildConsole MyWksp /prj="*"

<Package> can be VC, C#, BuildTools, DevToolAcc, XGE, Xbox One, PlayStation, Cafe, 3DS, KlocWorkPro or Coverity. In addition, the following cores packages are supported: 4Cores, 8Cores, 12Cores, 16Cores, 24Cores, 32Cores, 48Cores and 64Cores.

Use /SETENV several times to set/override multiple variables.

The default behavior is to write the build results, as seen in the Output display of the Build Monitor.

Value may be surrounded by quotes.

• To set this option globally, use the Agent Settings dialog  box > Visual Studio Builds > Advanced > Use environment variables instead of IDE paths option.

• If a build is initiated from a Visual Studio IDE window instantiated using the devenv.exe "/useenv" command line option, this build will always use "/useenv".

By default, Incredibuild uses Devenv to perform the build. Using this switch, Incredibuild will use MSBuild which will enable the option to add specific MSBuild flag using the /msbuildargs as can be seen below.

This will automatically use the 64 bit MSBuild for VS 2022 and later, and the 32 bit MSBuild for earlier VS versions.

To ignore this automatic detection and manually specify which version to use, add =32 or =64 (e.g. /usemsbuild=32)

<Version> can be one of the following: vc8 (for VS2005), vc9 (for VS2008), vc10 (for VS2010), vc11 (for VS2012), vc12 (for VS2013), vc14 (for VS2015), vc15 (for VS2017), and vc16 (for VS2019).