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: URGENT: Changing MSI filename of a 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 08, 2011
02:40 PM
URGENT: Changing MSI filename of a Merge Module
Hi,
I'm having trouble adding a VC++ 2010 CRT Merge Module to my IS 2010 project.
As our Product Name (GTA IV: San Andreas) has a colon ( : ) in it, it fails to build the MSI of the Merge Module, because it tries to build it using the Product Name:
And since filenames don't support colons, it throws up an error.
The install folder and such have all been changed to "GTA IV San Andreas".
How can I specify a different name for the MSI file to be included in the build?
I don't want to change the Product Name, as there are too much dependencies on this, also outside the InstallShield project.
(Sorry for the urgency, but this product is due asap)
Thanks in advance!
Kind regards,
Martijn van Berkel
I'm having trouble adding a VC++ 2010 CRT Merge Module to my IS 2010 project.
As our Product Name (GTA IV: San Andreas) has a colon ( : ) in it, it fails to build the MSI of the Merge Module, because it tries to build it using the Product Name:
E:\InstallShield 2010 Projects\GTA IV San Andreas\Media\Release Separated\Disk Images\MsiStub\{325CA968-C1FB-4A46-8BEE-DB7041738788}\GTA IV: San Andreas.msi
And since filenames don't support colons, it throws up an error.
The install folder and such have all been changed to "GTA IV San Andreas".
How can I specify a different name for the MSI file to be included in the build?
I don't want to change the Product Name, as there are too much dependencies on this, also outside the InstallShield project.
(Sorry for the urgency, but this product is due asap)
Thanks in advance!
Kind regards,
Martijn van Berkel
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 08, 2011
03:26 PM
I would not suggest avoiding the merge module holder object in InstallScript projects. Instead either use LaunchApplication (or related) to install the vcredist executable package, or if you think the ref counts are better handled when this is installed via merge module, create a Basic MSI that consumes the merge module, and install/uninstall that msi during installation and uninstallation.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 17, 2011
09:20 AM
Thanks for your reply!
I made the DLL files that were required install to the application folder. Since the application that needed the runtime searches for the DLL file in the current folder first, this method works.
Kind regards,
Martijn van Berkel
I made the DLL files that were required install to the application folder. Since the application that needed the runtime searches for the DLL file in the current folder first, this method works.
Kind regards,
Martijn van Berkel
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)