TurboFisch
Pilgrim

mergemodule path from ini file

I set this in my ini file:

[Mode]
StopOnFirstError=yes
Silent=no
Verbose=yes
WarningAsError=no
MergeModulePath=C:\Progr......

However, the mergemodule path did not take effect, instead it used the one that was defined in options dialog on the merge module tab.

WHat's wrong?
Labels (1)
0 Kudos
3 Replies
DebbieL
Pilgrim

The following help topic explains the order that InstallShield uses at build time to find merge modules that need to be included in releases.
Specifying the Directories that Contain Merge Modules

The merge modules that are specified in the Options dialog box take precedence over anything that is specified in the .ini file.
0 Kudos
TurboFisch
Pilgrim

I want a way to override the merge module path. A global setting like the options dialog just get's in the way. I think it is ok to use that as the default.

For one thing, testing has not finished so I don't want to publish to a location that can affect other projects.

I basically want a way to point my merge module paths to a recent build output directory and not to the global repository.

Can I use variables in the "options" tab?
0 Kudos
DebbieL
Pilgrim

Yes, you can use path variables on the Merge Modules tab, as in the following example:
\Modules\i386,\MyCustomModules
0 Kudos