Can any one tell me how add License agreement for before installing prerequisites in installshield 2010.
If you want, you can move your prerequisite as as "Feature Prerequisite". The feature prerequisite is tied to a specific feature on your product. You can then update your License Agreement to include any information with regards to your prerequisite.
One option might be to not install the programs as prerequisites, but launch them directly from your UI? After the dialog that displays the license agreement, have a custom dialog that displays the status of the other installers. Use the LaunchAppAndWait method to execute the other installers.
I don't know that this is possible. By definition, the prereqs run before any of the UI.
Related
I would like to run one installer for three programs, i.e. Folder is created under the name KAM Package, and there are three separate folders with three separate programs and their files. They must also be separately in the start menu.
Welcome to Stackoverflow: Please try to elaborate your questions and make them as specific as possible so we don't end up writing stuff that doesn't help or answer anything of what you really intended to ask about (happens more often than we'd like).
Deployment Tools: As others have said, please choose a deployment tool first. I'll just link to a previous answer to see if it helps you: How to create windows installer (links to Windows Installer tools and legacy setup tools - please do have a look).
Free MSI Tools: And there are free tools you can use to inspect compiled MSI files: Orca, InstEd or SuperOrca (towards bottom). These are not full-fledged tools to create MSI files, but they work great as viewers and for small hotfixes and changes, etc...
Some Links:
Wrap C# application in .msi installer
Windows service NOT shown in add remove programs under control panel
What installation product to use? InstallShield, WiX, Wise, Advanced Installer, etc
I have two installshield projects, I want to ask is it even possible to wrap an existing ism project within a wrapper ism project?!
The desired functionality is:
When i use custom installation and select to install the nested project it will behave as like i used it's native installer.
I'm using installshield 2011 Professional edition.
Thanks for helping.
I encountered this SAME problem. I wanted an installshield project to run another installshield project (which was an updater) to bring the software up to date before installing the first installer.
I solved this by creating a batch file.
1) The user launches the install msi.
2) The installer prerequisites detects that "previous version must be installed" by checking the registry and runs the batch file
3) The batch file kills the current process of installer and runs the second installer
4) Once the second installer is finished, the batch file re-runs the first installer (by using the batch command START /WAIT, which waits for a process to finish)
5) Now that the second installer was installed, the prerequisites doesn't trigger, and you resume with the installation.
You can, with caveats. If both of your projects are Basic MSI or InstallScript MSI, you will encounter the limitation that Windows Installer will only allow one MSI at a time. The end result of that is you can either run both safely through actions in the UI sequence (and fail if they are run silently), you might be able to use MSI Chaining (which I don't personally recommend), or turn one of the MSI packages into a prerequisite, or you have to find another way.
One option could be to add a third project, a pure InstallScript project, as a wrapper. If you go down this route, you have to consider what user experience you want for installation, maintenance, and uninstallation, including deciding what shows up in Programs and Features. Note that in later versions of InstallShield the Suite or Suite/Advanced UI project type is designed for this, but only in the Premier edition. (The Advanced UI project type in the Professional edition only allows for one main package, and you have two already.)
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 am developing an InstallShield InstallScript project (not MSI) and currently working on the "updatemode" behaviour of the setup.exe program.
I would like to know if it is possible to ignore the update of one specific feature and still update the other ones.
The problem is that the program needs to determine whether the feature should be updated during the execution, which means the feature has to be embedded in the update program.
I've already tried to use the InstallScript function FeatureSetItem, but when I set my feature to false, the feature is not ignored, but uninstalled by my update program.
Any idea would be helpful.
Not sure what it is that you don't want to be updated or why, but if it's just files then set the components for the feature to "overwrite by date" or "overwrite by version".
In InstallShield, go to "Releases". Create a new "Release" and then go through the Release Wizard.
One of the windows in the release wizard allows you to check/uncheck the features for that release. Simply uncheck the features that you do not want to update. This way, those features will not be included when you build that particular release configuration. They will still be included if you build using the original release configuration.
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.