we are using the Installshield which comes with visual studio, my engineer told me that it is a Installshield express
my engineer has created an installation program, if the software has already been installed, then when a user run the installation program again it shows REPAIR, MODIFY and REMOVE options.
the problem is that REPAIR and MODIFY is actually useless to me.
Can I remove these 2 options? such that when a user run the installation program while a software is already installed, it will just prompt the user to confirmation uninstall the software?
My engineer told me that this is not feasible with the bundled Installshield version. Is this true?
Thank you very much.
John
I don't sure if Express version has User Interface\Dialogs menu, but if has. Then it's possible, just remove Repair\Modify buttons from Maintenance dialog.
Related
I have created an MSI installscript project in Installshield. I went to Project Assistant>Application Files, then added the application files(package) and built Setup.exe to install.
After installed these files, I went back to Project Assistant and added some application files, then i changed the product version for updating. Finally, i built the Setup.exe again. When i run the Setup.exe, the automatic update (Upgrade Window Installer Setup) asked me to update a new version. After finishing, I checked Program Files(x86) and the updating didn't do anything, the old package was still here.
How can i update my new package? Is there any way to disable the Upgrade Window Installer Setup?
Thanks for the help.
In my humble opinion, most likely, you added new files to existing Component with keypath, which didn't change. Also you should check "Add\Remove Programs" snap-in in Control Panel to see if upgrade was applied - there should change version of your product.
So, I recommend you check Components, and re-allocate files to new Components if I had right. Also please read more about Components and Files. Could start from here.
Two words about InstallScript MSI project. From InstallShield documentation: Because this project type uses two different engines, it is more complex than pure InstallScript or Basic MSI installation projects. It is recommended only for advanced users.
So, if possible, use Basic MSI project - it's a bit simpler than InstallScript MSI for begginers.
I have an InstallScript setup created with IS 2011, which includes prerequisites: The prerequisites dialog immediately appears after executing setup.exe even before the welcome dialog.
Is there a way to change this behavior so that the prerequisites are installed at a later step during the setup e.g. when the real setup procedure is started (i.e. after the welcome dialog, license agreement, ...).
Also I want to avoid the prerequisites installation when my application is already installed and I execute setup.exe and choose the uninstall option.
InstallShield offers a scheduling for prerequisites that is kicked off after the Install button. This approach is called "Feature Prerequisites" in the InstallShield help. Do be aware that since the .msi is already running, it is a more complicated time, so certain prerequisites should not be scheduled there (and others may fail to serve their purpose if installed after the wizard panels).
In InstallShield 2012 and later, the suite project type supports installing multiple packages after a single wizard. In that model, prerequisites are just another package, and your use case is more directly supported.
Being forced to use the garbage version of LE in VS 2012, I cannot get things to build because it is telling me that my install folder path is too long. It literally looks like it is creating the same path, verbatim, inside of another folder. First this fails on the DVD so can I disable that? Second, this appears to be controlled by the variable ISProductFolder but I cannot find how to modify that location.
Can somebody please help?
Well, it is not surprise that each setup tool has its problems. Please note that there are no tools which can accurately detect your application dependencies. The best a tool can do is make suggestions. This is why most setup developers determine the dependencies themselves and manually include them in the installer.
If you're not happy with InstallShield, you can try a different setup tool: http://en.wikipedia.org/wiki/List_of_installation_software
The free version of Advanced Installer includes a Visual Studio setup project which may help.
I have multilingual installation setup program, where user can select 5 different language. Consider I have installed application in German language. whenever I am uninstall the application or update the previous setup it is launching in German. I would like to know how setup will detect the older installation product language.
In my case I have created a upgrade only installation where it will detect the previous version of the installation and do the major upgrade. In the major upgrade I don't want to display the language dialog. The update should happen in the earlier installed lanugage.
Does installscript has any API to detect the earlier installed applications product language.?
I belive there should be some way to do like that as uninstallation does, Can any body give me some suggestion.
Thanks in advance.
For a pure InstallScript installation, this is tracked in the uninstall key's command line. Look for the /L parameter.
For Windows Installer-based installations, this is remembered automatically by Windows Installer tracking which transforms are applied at initial installation. This includes the language transform.
How can I add a 'restart' checkbox after instalation completes in my InstallShield project?
Check if this previous SO answer does the trick: How to force restart after uninstall for a Basic MSI Project in InstallShield 2009 Premier
Note that i haven't flagged this as a duplicate because there are different flavors of InstallShield and you haven't said which you are using.
Edit: the InstallShield doco also suggests using the SdFinishReboot dialog which is instantiated via script. Here are a couple of links: SdFinishReboot, SdFinishReboot sample