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: Force Installshield to leave .msi after building .exe
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
‎Dec 17, 2012
12:26 PM
Force Installshield to leave .msi after building .exe
Hi,
Due to legacy issues we're forced to build both .exe and .msi installers for several of our projects. Right now we build two times, which result in the installers having different ProductCodes and PackageCodes. We see from the build process that the .msi is created first, then signed, then finally moved into the .exe installer. Is there some way to force Installshield to leave the .msi file in place, so we get both installer types?
Due to legacy issues we're forced to build both .exe and .msi installers for several of our projects. Right now we build two times, which result in the installers having different ProductCodes and PackageCodes. We see from the build process that the .msi is created first, then signed, then finally moved into the .exe installer. Is there some way to force Installshield to leave the .msi file in place, so we get both installer types?
(3) Replies
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 17, 2012
07:56 PM
Hi, Ymgvee
You can try to disable Generate Package Code settings in * Product Configuration of Release viewer.
You can try to disable Generate Package Code settings in * Product Configuration of Release viewer.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 18, 2012
05:27 AM
Thanks, and we might try that if there is no other option.
Are there any problems with creating two different installations (that install the same content, but are built separately) with the same ProductCode and PackageCode? I've seen some warnings about re-using the package code, but what are the implications?
Are there any problems with creating two different installations (that install the same content, but are built separately) with the same ProductCode and PackageCode? I've seen some warnings about re-using the package code, but what are the implications?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 31, 2013
04:24 AM
Sorry for the necro, but I see no answer to the final question.
This is exactly what I do and have had no issues. We build two installer packages for each build, one a raw .msi and the other a Setup.exe. If there is a way to just insert the raw .msi into the Setup.exe I never found it. So I just disabled the automatic spinning of the package code in the release configuration and build it twice.
The Product code isn't spun automatically, I spin this manually along with the Package code only when we move to the next version. All my Upgrades are major ones.
This is exactly what I do and have had no issues. We build two installer packages for each build, one a raw .msi and the other a Setup.exe. If there is a way to just insert the raw .msi into the Setup.exe I never found it. So I just disabled the automatic spinning of the package code in the release configuration and build it twice.
The Product code isn't spun automatically, I spin this manually along with the Package code only when we move to the next version. All my Upgrades are major ones.
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)