This custom action sets the install directory from a formatted text string. For more information, see Changing the Target Location for a Directory
Source
The Source field of the CustomAction table contains a key to the Directory table. The designated directory is set by the formatted string in the Target field using MsiSetTargetPath. This sets the target path and associated property to the expanded value of the formatted text string in the Target field. Do not attempt to change the location of a target directory during a maintenance installation. Do not attempt to change the target directory path if some components using that path are already installed for any user.
Type Value
Include the following value in the Type column of the CustomAction table to specify the basic numeric type.
| Constants | Hexadecimal | Decimal |
|---|---|---|
| msidbCustomActionTypeTextData + msidbCustomActionTypeDirectory | 0x023 | 35 |
Target
The Target column of the CustomAction table contains a text string formatted using the functionality specified in MsiFormatRecord (without the numeric field specifiers). Parameters to be replaced are enclosed in square brackets […], and may be properties, environment variables (% prefix), file paths (# prefix), or component directory paths ($ prefix). Note that directory paths always end with a directory separator.
Return Processing Options
The custom action does not use these options.
Execution Scheduling Options
Include optional flag bits in the Type column of the CustomAction table to specify execution scheduling options. These options control the multiple execution of custom actions. For a description of the options, see Custom Action Execution Scheduling Options.
In-Script Execution Options
The custom action does not use these options.
Return Values
See Custom Action Return Values.
Remarks
If you set a private property in the UI sequence by authoring a custom action in one of the user interface sequence tables, that property is not set in the execution sequence. To set the property in the execution sequence you must also put a custom action in an execution sequence table. Alternatively, you can make the property a public property and include it in the SecureCustomProperties property.
See Also
Send comments about this topic to Microsoft
Build date: 8/13/2009
© 2009 Microsoft Corporation. All rights reserved.