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
- :
- Modifying setup.exe after it was built
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
‎Oct 25, 2018
06:35 PM
Modifying setup.exe after it was built
Our product relies on modifying VERSION resource information on the setup.exe to personalize the installation for our customers.
Everything worked fine until we purchased IS 2018. The setup.exe built in IS 2018 becomes unusable (size changes from 8Mb to 1.2Mb).
On top of it after installing IS 2018 our IS 2010 deactivated itself so we no longer can build installation packages for production.
Please help!
Everything worked fine until we purchased IS 2018. The setup.exe built in IS 2018 becomes unusable (size changes from 8Mb to 1.2Mb).
On top of it after installing IS 2018 our IS 2010 deactivated itself so we no longer can build installation packages for production.
Please help!
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 28, 2018
09:06 AM
sk1f23 wrote:
Our product relies on modifying VERSION resource information on the setup.exe to personalize the installation for our customers.
Everything worked fine until we purchased IS 2018. The setup.exe built in IS 2018 becomes unusable (size changes from 8Mb to 1.2Mb).
On top of it after installing IS 2018 our IS 2010 deactivated itself so we no longer can build installation packages for production.
Please help!
Hi ,
Can you please explain a bit more to understand the issue?
-What do you want to acheive from InstallShield-IDE?-Version change ?
-The setup.exe built in IS 2018 becomes unusable (size changes from 8Mb to 1.2Mb). -Unusable means what?-Is it IS2018/IS2018-SP1/IS2018-R2?
-On top of it after installing IS 2018 our IS 2010 deactivated itself so we no longer can build installation packages for production. ?-It may not be the case how installshield deals with licensing.Different products can co-exist on same machine?
Thanks,
Jenifer
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 29, 2018
09:58 AM
"On top of it after installing IS 2018 our IS 2010 deactivated itself so we no longer can build installation packages for production. "
If you happen to be building from TFS... keep in mind that TFS will use the last version of InstallShield that was installed or repaired.
If you happen to be building from TFS... keep in mind that TFS will use the last version of InstallShield that was installed or repaired.