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: stand alone build cannot find custom merge module
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
‎Aug 03, 2008
03:38 PM
stand alone build cannot find custom merge module
I am using IS2008 to create a basic msi. My problem is that I am using VS team fouundation to build a Vs solution that includes my IS project and it cannot find my merge modules that are create and stored in c:\MergeModules. For various reasons I do not want to store my custom MM in another location. Is there a way to add the path c:\MergeModules to the stand alone build path, similar to the way I do in the IS development environment?
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 04, 2008
08:19 AM
You'll want to pass the merge module path through the -o command-line parameter. Here's a link to a help topic that describes that parameter, plus others:
Standalone Command-Line Build
Standalone Command-Line Build
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 04, 2008
09:11 AM
Thanks for the info and I may have to change to use a cmd line. However I am using Microsoft Team Foundation to build my solution. My IS projects are part of the solution so I do not use the cmd line to be able to add -o "path". On my desktop I open a visual studio solution and click rebuild all. My C# projects are built and then my IS 2008 projects are built. I want to duplicte this on my build machine using Stand alone build.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 04, 2008
10:51 AM
Oh, sorry! I misunderstood your requirements.
In InstallShield.targets, there's a line in the InstallShield task that looks like this:
MergeModulePath="@(InstallShieldMergeModulePath)"
Therefore, creating an ItemGroup with the name InstallShieldMergeModulePath should result in a similar behavior to the -o option. Generally you'd add this ItemGroup to the .isproj file.
In InstallShield.targets, there's a line in the InstallShield task that looks like this:
MergeModulePath="@(InstallShieldMergeModulePath)"
Therefore, creating an ItemGroup with the name InstallShieldMergeModulePath should result in a similar behavior to the -o option. Generally you'd add this ItemGroup to the .isproj file.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 04, 2008
11:01 AM
FANTASTIC! That is what I am looking for. Is there any documentation or Tips and Tricks that you know of for the isproj file?
Thanks:)
Thanks:)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 04, 2008
11:08 AM
The following help topic has some info:
http://helpnet.acresso.com/Robo/BIN/Robo.dll?tpc=/robo/projects/installshield15helplib/MSBuild.htm
Searching the InstallShield forums for ISPROJ may reveal some more tips.
http://helpnet.acresso.com/Robo/BIN/Robo.dll?tpc=/robo/projects/installshield15helplib/MSBuild.htm
Searching the InstallShield forums for ISPROJ may reveal some more tips.
![](/skins/images/B841502EC6C60E3ACD181F0696AD21B9/responsive_peak/images/icon_anonymous_message.png)