About gbaltazar

gbaltazar · ‎Oct 11, 2018

I currently have IS 2018 Premier SP1 installed. If I update to IS 2018 R2, will all of my existing .ism project files need updating as well? Will there be an IS 2018 R2 Standalone Build Component?

gbaltazar · ‎Jun 11, 2018

Add the exe you want to run along with its supporting files in the "Support Directory" (i.e. Support Files -> Language Independent). You can then execute the .exe from that location, from InstallScript code, it will look like: LaunchAppAndWait(SUPPORTDIR ^ "your.exe", LAAW_OPTION_WAIT) or something similar.

gbaltazar · ‎Apr 12, 2018

"Control Themes" is the help topic you need. I too needed to do this for my install.

gbaltazar · ‎Apr 12, 2018

I'm not sure if this is possible, but I'd like to know as well if anybody else was able to make this work...

gbaltazar · ‎Apr 09, 2018

I suggest you take a look at the StrSub function. You would have to figure out the start and end indexes (assuming the filename you are removing is of constant length) but it would give you the value you would want.

gbaltazar · ‎Oct 10, 2017

Try DeleteFile(szPath ^ "*.*");

gbaltazar · ‎Jun 13, 2017

Hello there, what exactly did you do to achieve this? I too want this behavior for my installer. Thanks.

gbaltazar · ‎Jan 04, 2012

use launchappandwait to call msiexec.exe and then feed it the switches to launch your msi.

gbaltazar · ‎Oct 21, 2010

This really depends on the application you are installing. If the future release has 64-bit components, then you may have to create a separate 64-bit installer.

gbaltazar · ‎Oct 21, 2010

I ran into this problem about a year ago. Before I figured out that .pfx files worked, I was using a signcode window monitoring tool to automatically fill in the certificate password if ever the signcode window popped up. I've since converted to .pfx files and haven't looked back since.

gbaltazar · ‎Oct 20, 2010

You can't run two basic msi installers concurrently. The windows installer engine will not allow it. The best approach is to uninstall the applications seperately and not within another installation.

gbaltazar · ‎Oct 20, 2010

You won't be able to initialize more than one msiexec process during the Execute Sequence. That is why your quiet mode custom actions will fail. What you can do is create a setup launcher that can send uninstall commands to your language packs, then calls your main app installation/uninstallation.

gbaltazar · ‎Oct 15, 2010

On 64bit systems, you have to use REGDB_OPTIONS = REGDB_OPTIONS | REGDB_OPTION_WOW64_64KEY if you want to check the 64bit hives. Otherwise, the current check will look at the syswow64 instance of HKLM.

gbaltazar · ‎Oct 13, 2010

Use the SELECTED_LANGUAGE variable and compare it with the InstallScript Language IDs (e.g. ISLANG_ENGLISH). From there I'm sure you can get the language code also...

gbaltazar · ‎Oct 12, 2010

Try creating separate control events for service stop and service uninstall.

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:11 PM

Upgrading IS2018

Re: Running external application from inside Installshield

Re: Suite footer buttons, change color?

Re: How to remove InstallShield water mark in Suite installer

Re: Setting a property with a substing of a value retreived from the registry...

Re: Delete(FilePath\.) not working

Re: Suite - Don't allow Maintenance Mode

Re: Launching a third party MSI package.

Re: Installer for 64-bit OS

Re: Code signing and build automation to date

Re: How to invoke a Basic MSI installer from another Basic MSI installer silently

Re: Install Main Applcation + install language update and uninstall all of them

Re: RegDBKeyExist Fails

Re: Retrieve Setup Language in InstallScript

Re: Stop and delete service is not working in uninstall.