How to have MSMs copied to Merge Module directory

FinalBuilder Discussion
1

I am trying to create an InstallShield action that would copy newly created merge modules to the merge module directory.

The merge modules InstallShield files I have have the option set to copy the newly built .MSM file to the merge module directory. However, when I create an InstallShield action to build the merge module, it is not copied to the merge module directory.

I’ve tried creating an InstallShield Windows Installer Project action as well as an InstallShield Developer Project action. I am using InstallShield version 12 - Premier Edition.

Is there an option I need to set/select to accomplish this task? Thanks in advanced for your help!!!

2

Tracey,

I am not an expert in IS 12. Are you building using the full version or do they have a stand alone build version of IS 12 available? You could try running the stand alone build version using the command line to see what the result is.

As a work around you might do the copying in FB. Just find msm file and copy it to the desired folder.

HTH

3

Thanks for your reply Raoul. I’ve already implemented the work around for a few of the merge modules my script creates. However, this is going to add an additional task to every merge module generated (and we have hundreds). I just assumed there was something I had not set or done to allow FinalBuilder to copy the merge module as specified within the InstallShield script.BTW, I tried this with both the full version of IS and with the standalone build tool.I’ll keep playing around with it until I get my desired results…even if it means running the cmd line via an Execute Program action.Thanks again!!!

4

Hi Tracey,

Glad you got a workaround for it. Let me know if there’s another command line argument we can add to the InstallShield action that can do this merge module copying automatically.

cheers,
tate.

5

Tracey,

can’t you use a define fileset or file iterator with *.msm in the project folder of your installshield project to locate the generated msm and just copy that using a copy fileset action?

HTH

6

Hey guys,

Found out what I needed to do…

[1] In the “Stand Alone” tab of the InstallShield Developer Project action, the comma seperated paths listed in the “Merge Module Path” must be individually double quoted. This is especially true if the path contains spaces. The first path is what is selected as the path to copy the MSM file.

Note:
The copy will only work if IsSABld.exe is set as the IS executable. This is because it has the -o option w/in InstallShield (hence the “Stand Alone” tab in FinalBuilder).

Count this as user errror (as I suspected). :slight_smile:

Would it be possible to add the double quoting requirement to the FB docs? Might be helpful to newbies (of both IS and FB).

7

Thanks Tracey - I’ve updated the help.