Path

This command updates "path like" environment variables. To do this it populates the MSI "Environment" table .

The macro takes these parameters:

• The PATH (positional)
  This is almost always a directory path to be added. This could be an absolute name but can also be something like "[TARGETDIR]". It would be rare to "hard code" a directory as the user could change the installation directory when installing. This item does not have to be a path (if "NAME" is supplied), it is simply the "item" being added.

• Name (optional)
  This is the name of the "path like" environment variable. The default variable name is "PATH".

• Delimiter (optional)
  For normal use as a path separator the default value of ";" (semi-colon) will do however if you need to change the delimiter to character string you can do so.

• AtEnd (optional)
  Do you want the directory added to the start or the end of any currently existing path (use 'Y' for end, otherwise 'N').

  The default for this parameter can be set via the DEFAULT_ENVIRON_PATH_ATEND macro. This is initially "Y".

• System (optional)
  An environment variable can be system wide or per-user. Set to "Y" if system ('N' if not).

  The default for this parameter can be set via the DEFAULT_ENVIRON_SYSTEM macro. This is initially "Y".

• Component (optional)
  This is the name of a component, if not supplied and if this command is nested between "component" and "/component" commands then the name of the "current" component is used. The component's attributes control installation and uninstallation conditions and behaviour.

• How (optional)
  This provides more information about how the environment variable is to be manipulated, unlike most other attributes this is a string of concatenated characters (ie a Microsoft "oops").

  This parameter should be passed a comma separated list of one or more of the following values:

  • SET_DURING_INSTALLATION
  • DELETE_ON_INSTALL
  • DELETE_ON_UNINSTALL
  • CREATE_IF_NONEXISTANT
  Not all combinations are valid.

  The default for this parameter can be set via the DEFAULT_ENVIRON_HOW macro. The initial value is "SET_DURING_INSTALLATION, DELETE_ON_UNINSTALL".

• RowKey (optional)
  You may wish to set up a specific key to the row in the "Environment" table , if you don't choose one a unique key will be generated for you.

To pick up the changed environment variables the user may need to logoff and logon (user environment variables) or reboot (system environment variables). This is because the variables are per-process and will not normally change until the process is restarted at which time it typically inherits the parent processes environment.

Windows Installer will broadcast the "WM_SETTINGCHANGE" message (lParam set to the string "Environment") to all top level windows so that these processes have the opportunity to update their per-process environment details if they so wish. It is a known Windows "feature" that the SCM (services) doesn't handle this message.

As a diagnostic aid, the "PROCESS EXPLORER" tool can show you the "process hierarchy" as well as each processes environment.

<$Component "Environment" Directory_="<$AnyDir>" LM="Y">
 ;--- Test environment macro (create in install, remove in uninstall) -----
 <$Environment Name="EnvVarLit" VALUE="Value4EnvVar1"> ;;Assign literal
 <$Environment Name="EnvVarExp" *VALUE="WeekDayName(WeekDay(date()))"> ;;Assign result of VBSCRIPT expression
<$/Component>
<$Component "SomeExistingComponentJustAsAnExampleOfHowToDoIt">
 ;--- Test PATH macro -----------------------------------------------------
 <$Path "C:\Some\Path"> ;;Normally update "PATH"
 <$Path "[TARGETDIR]"> ;;Refer to MSI directory/property
 <$Path ".REX" NAME="PATHEXT"> ;;Update another type of "path like" environment
<$/Component>

Have a look at the following bugs:

1. PATH Completely Cleared!
2. PATH Update Flakey in WIN95/98

Note that the value will end with a slash, if this causes problems with your program then I'd suggest you fix your program, however if its someone else's then see the "Trailing Slash Removal" section for an example that uses a custom action or perhaps a better way is to use "." (for "current" directory), for example:

<$Path "[INSTALLDIR]." System="N">

---