The Custom Commands dialog box contains the following options:

• Command List —The current list of custom commands the installer will execute.
• Add —Adds a new command to the Command List by duplicating the selected command in the list.
• Delete —Deletes the selected command in the Command List.
• Move Up —Moves the selected command up in the Command List.
• Move Down —Moves the selected command down in the Command List.
• Command Directory —The directory where the command is located for the selected command in the Command List.
• Command and Arguments —The command and the command-line arguments for the selected command in the Command List. You can use the following case-insensitive directory macros in the command to avoid using fixed paths when you specify the command or the command arguments on different computers:
  Note When you deploy on Windows 10/8.1/7, the name of the < user > subdirectory depends on the user account you use to elevate to administrator privileges.
  Note To execute command-line commands, a custom command must invoke the cmd.exe executable to execute the command. For example, to execute the del command, use the custom command cmd /c del <FilePath> . Command-line commands which call an executable in the system directory, such as xcopy , can be executed directly or through cmd.exe .

  Macro	Directory	Example
  <ALLUSERSPROFILE>	Profile directory for all users.	(Windows 10/8.1/7) C:\ProgramData
  <DESKTOPDIR>	Directory for the desktop of the current user.	(Windows 10/8.1/7) C:\Users\< user >\Desktop
  <INSTALLATIONDIR>	Destination directory the user selects in the installer. Note Not all installers use this macro.	C:\<Program Files>\Company Name\Project Name
  <INSTALLERDIR>	Directory where the installer was started.	D:\<Program Files>\< My Application >
  <NIDIR>	Directory where National Instruments products reside. (64-bit TestStand) Refers to the 64-bit directory for deployments you build with the 64-bit TestStand deployment utility.	C:\<Program Files>\National Instruments
  <PROGRAMFILES>	System program files directory. (64-bit TestStand) Refers to the 64-bit directory for deployments you build with the 64-bit TestStand deployment utility.	C:\<Program Files>
  <PROGRAMMENU>	Directory where the Start menu entries reside.	(Windows 10/8.1/7) C:\ProgramData\Microsoft\Windows\Start Menu\Programs
  <STARTUPDIR>	Directory where the Startup menu entries reside.	(Windows 10/8.1/7) C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
  <SYSTEMDRIVE>	Disk where Microsoft Windows is installed.	C:\
  <SysWOW64>	Directory for 32-bit operating system DLLs on 64-bit Windows. Note Applies only to 64-bit installers.	C:\Windows\SysWOW64
  <TEMP>	Temporary directory the GetTempPath Windows API function returns. Refer to Microsoft MSDN documentation for more information about the GetTempPath function.	(Windows 10/8.1/7) C:\Users\<user>\AppData\Local\Temp
  <TESTSTAND>	TestStand directory for the version that created the installer. (64-bit TestStand) Refers to the 64-bit directory for deployments you build with the 64-bit TestStand deployment utility.	C:\<Program Files>\National Instruments\<TestStand>
  <TSAPPDATA>	Directory that contains configuration files users generally do not edit but a program can edit. (64-bit TestStand) Refers to the 64-bit directory for deployments you build with the 64-bit TestStand deployment utility.	(Windows 10/8.1/7) C:\ProgramData\National Instruments\<TestStand>
  <TSPUBLIC>	Directory that contains user modifications and customizations. (64-bit TestStand) Refers to the 64-bit directory for deployments you build with the 64-bit TestStand deployment utility.	(Windows 10/8.1/7) C:\Users\Public\Documents\National Instruments\<TestStand>
  <USERPROFILE>	Profile directory for the current user.	(Windows 10/8.1/7) C:\Users\<user>
  <WINDIR>	Windows directory.	C:\Windows
  <WINSYSTEM>	Windows System directory.	C:\Windows\System
  <WINSYSTEM32>	Windows System32 directory.	C:\Windows\System32

• Request Reboot After All Commands Execute —When you enable this option, the installer prompts the user to reboot after all custom commands execute, such as when National Instruments or third-party installers require the computer to reboot.
• Show Commands Progress Window —When you enable this option, the installer opens a window that displays the currently executing custom command and previous command results. Use this option to troubleshoot the custom commands.
• Skip Custom Commands When Installing Silently —When you enable this option, the installer does not execute custom commands when you run the installer executable with the /q command-line argument to run the installer in silent mode. Use this option to skip custom commands that require user interaction.

See Also

Deploying TestStand Systems

TestStand Deployment Utility

TestStand Directories

Using Custom Commands to Execute Third-Party Installers