Standalone Build fails where others succeed!

[Jizzle2000]

Sweetness!!! *The clouds part, angels sing and the sun shines* I greatly appreciate your response and attention to this issue. Thank you very much and I look forward to hearing of a fix eventually.

[Dennis Marks]

We use the StandAlone Builder extensively here, by a build tool that was developed and supported my INSTALLSHIELD! We have no problems with any of our other applications building in previous release to use a common merge/object folder of our choosing. A matter of fact We even go into the IDE download the item required and update accordingly, with one exception to the OLEDB21 where we have to use MSIFILER to file in MSIFILEHASH information so we do not required orgininal source media due to a simple merge module!. Installshield 11.5 has a bug that the other version do not have. IF I work fine in the IDE and move the ISM to our Build machine that has only SAB and copy the common location on the box it should work fine but it does not! We choose a common location and NOT have to modify different locations everytime we need to update redistributable for our applications. The ISM file should know where the files that it pulls into the package is and not some ini file in the objectgallery! Installshield X seems to be better for SAB then what we are finding with INSTALLSHIELD 11 or 11.5!

[rquesada]

tnx!
Something similiar was happening to me, I've fixed copying (not moving) the .msm to the Objects folder.

riq.

[myg_qc]

Originally Posted by SherylSikora

I would like to take this opportunity to clear up some confusion regarding how the StandAlone Build handles objects and merge modules.

As a rule, if the .msm file you are using is classified as an object, the files should be placed in an "Objects" folder under the StandAlone Build install location. An example of this would be the MDAC 2.7 object that was mentioned. If the .msm file is classified as a merge module, the file should be placed in an "Modules\i386" folder. An example of this type of file would be the Crystal Report Engine API.Msm.

The "ObjectsGallery" folder should not be deleted because some of the objects need those .ini files to determine where to find their dependant binaries, which are needed to build those objects. An example of one of these objects would be the DirectX 9 object.

I appreciate your suggestion that the "Objects" folder should be created by the install to help guide the user and I have created Issue # IOC-000045751 for this.

In addition, an underlying issue is causing the –o command line parameter to not work as you expect it to. As a workaround, if you want to use the –o parameter to specify your own location for your objects and merge modules you will need to copy those files from your InstallShield 11.5 install location into the StandAlone Build install location into either a folder named “Objects” or “Modules\i386” as I described above. You can then specify any path you want on the command line using the –o parameter and the build will use it. This is an unnecessary duplication of these files so I have created Issue # IOC-000045700 for this.

Thank you for your suggestions and your feedback.

Could you tell me when the fix for Issue # IOC-000045700 will be available, without it I couldn't continue using IS 11.5 for my install, I really need it thanks.

[SherylSikora]

Issue IOC-000045700 is scheduled to be fixed for the InstallShield 12 release. But until then the workaround that I suggest in my previous post should work for you.