InstallShield 2015
Project: This information applies to Basic MSI projects.
Depending on how the author of a DIM project defined the project’s path variables, it may be necessary for you to override their values when you build a Basic MSI release that includes that DIM. Otherwise, when you build the installation, you may encounter errors because of missing files, or the wrong files may be included in your build.
InstallShield offers several ways for overriding the path variables in a DIM project:
| • | If you are building a Basic MSI release and you want to override a path variable for a DIM that was imported into the Basic MSI project, you can use the Path Variable Overrides setting on the Build tab in the Releases view. |
| • | If you are building from the command line with ISCmdBld.exe, use the -l parameter to specify a path variable name and new value. Use this method if you are building an installation for a Basic MSI project that contains one or more DIMs. |
| • | If you are building through MSBuild or Team Foundation Server (TFS), use the PathVariables parameter on the InstallShield task. This parameter is exposed as the ItemGroup InstallShieldPathVariableOverrides when the default targets file is used. |
| • | You can open the DIM project and update values of path variables as needed. To learn how to open the DIM project from within an open Basic MSI project, see Opening a Referenced DIM Project from Within an Installation Project. |
At build time, InstallShield (or the Standalone Build) uses the path variable overrides that you set when obtaining the source files for your project and building the release.
For more information as well as tips on using path variables in DIM projects, see Using Path Variables in a DIM.
See Also
InstallShield 2015 Help LibraryJune 2015 |
Copyright Information | Contact Us |