This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: mergemodule path from ini file
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 05, 2014
05:28 PM
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?
[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?
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 08, 2014
08:50 AM
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.
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.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 09, 2014
11:58 AM
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?
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?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 10, 2014
09:20 AM
Yes, you can use path variables on the Merge Modules tab, as in the following example:
\Modules\i386,\MyCustomModules