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: Merge module dependencies
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
Nov 16, 2007
03:49 PM
Merge module dependencies
I'm a relatively new Installshield User.
My project is rather large.
My thought was I wanted to create my own merge module,
that would contain about 15 other merge modules, plus about 15 loose dll's.
so i'm able to compile the merge module, although it appears rather small to me (as if it only contains my loose files)
then i build a new installshield basic project, and just want to pick my merge module, and expect it to bring all the other dependencies in.
and it doesnt...
can someone tell me what i did wrong.
the idea is that all our apps need all the same requirements,
and i dont want someone to forget something.
so i want to just pick our own merge module on the list each time and that will be everything we need.
thanks. Jay
My project is rather large.
My thought was I wanted to create my own merge module,
that would contain about 15 other merge modules, plus about 15 loose dll's.
so i'm able to compile the merge module, although it appears rather small to me (as if it only contains my loose files)
then i build a new installshield basic project, and just want to pick my merge module, and expect it to bring all the other dependencies in.
and it doesnt...
can someone tell me what i did wrong.
the idea is that all our apps need all the same requirements,
and i dont want someone to forget something.
so i want to just pick our own merge module on the list each time and that will be everything we need.
thanks. Jay
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 19, 2007
07:49 AM
I think you're on the right track.
What do you mean when you say "that would contain about 15 other merge modules"? Do you mean that your MM has dependecies set for these other MMs?
I think that's the way to go. Your "master" module will contain only the "loose dll's" but any time you include it, the dependent MMs will also be pulled in.
What do you mean when you say "that would contain about 15 other merge modules"? Do you mean that your MM has dependecies set for these other MMs?
I think that's the way to go. Your "master" module will contain only the "loose dll's" but any time you include it, the dependent MMs will also be pulled in.