Circumstances play a important function in constructing a profitable Suite set up. The ideas beneath generally is a large assist and save time when utilizing InstallShield’s Suites builder.
Tip 1: Outline an Eligibility Situation for Every .exe Bundle to Stop Downgrades
InstallShield creates an eligibility situation mechanically for every .msi bundle within the Suite challenge by default; the eligibility situation checks to make sure that a later model of the bundle shouldn’t be already current on track techniques.
For .exe packages, you’ll need to mirror the identical conduct: create an acceptable eligibility situation to make sure that the Suite set up doesn’t downgrade your product by permitting an earlier model to put in over a later model.
Notice that in case your product helps side-by-side variations of, say, model 3 with model 4 on the identical system, be certain that your circumstances help this. In case your product doesn’t help these variations on the identical system, be certain that your circumstances block this situation.
Tip 2: Think about Defining an Eligibility Situation for Every Bundle to Verify for Necessities and Dependencies
A bundle could fail to put in or the product could not run as anticipated on track techniques that don’t meet its necessities (such because the minimal working system model) or that do not need its dependencies (such because the .NET Framework, Microsoft SQL Server, or a third-party library). To stop the Suite bundle from making an attempt to obtain (if relevant) and launch packages on a goal system on which they’ll fail, outline an eligibility situation that checks for necessities and dependencies. And each time you might have a bundle that accommodates a number of launch circumstances, be certain that you add corresponding eligibility circumstances to the bundle.
As a result of .msp packages require their goal .msi bundle to be current, create an eligibility situation that checks goal techniques for the presence of the product that you simply need to replace.
Tip 3: Evaluation the Default Exit Situation for Relevance
By default, whenever you create a brand new Suite challenge, InstallShield mechanically creates an exit situation that aborts the Suite set up if not one of the main packages are eligible for set up. The exit situation has an Eligible Bundle kind of situation verify, and it makes use of an asterisk (*) within the situation’s bundle ID setting as a placeholder for every main bundle’s ID.
You possibly can not directly management this default exit situation by modifying the eligibility situation of every bundle.
The default exit message assumes that your eligibility circumstances solely forestall downgrades. If any of the first packages in your challenge have an eligibility situation that checks for one thing else, it’s possible you’ll have to edit the default message to correctly mirror the rationale for the Suite set up aborting.
For instance, in case your Suite challenge consists of one 64-bit main bundle, this bundle could have an eligibility situation that checks for an x64 structure. On this case, it’s possible you’ll have to edit the exit message and situation to account for the truth that the bundle shouldn’t be eligible on a 32-bit goal system. Nonetheless, in case your Suite bundle consists of one 64-bit main bundle and one 32-bit main bundle, and also you configure the eligibility circumstances for these packages in order that the suitable one is launched on track techniques which have the corresponding structure, the default exit message and situation could also be appropriate as is.
Tip 4: Outline a Detection Situation for Every .exe Bundle
Each .exe bundle in a Suite challenge should have a minimum of one outlined detection situation. The detection situation ought to consider whether or not the bundle is already put in on track techniques. At construct time, InstallShield combines the detection circumstances from the entire main packages in a Suite challenge to type the Suite’s mode situation.
The Suite Setup.exe file can decide whether or not an .msi bundle within the Suite set up has already been put in on track techniques. It could additionally decide whether or not an .msp bundle within the Suite set up has already been utilized to an earlier model of the product. Subsequently, manually defining a detection situation for these two forms of packages shouldn’t be a requirement.
Tip 5: Be Very Express
Just remember to are creating circumstances for the entire doable outcomes; that means, you might have full management over the suitable conduct. For instance, in case you are checking for a particular model of a file or for a selected registry worth, ensure that to additionally verify for the existence of the file or registry entry. Typically a lacking file is ok however a given model variety of a file is unhealthy; typically a lacking file is unhealthy.
Check your circumstances on varied goal techniques and below completely different situations to guarantee that the Suite set up behaves as anticipated. Use clear machines, machines which have earlier variations of your merchandise, and machines which have the present model. Additionally contemplate mocking up a future model of your product to check that your present set up doesn’t downgrade future variations.
Do you might have any recommendations on circumstances so as to add? Are your circumstances easy or advanced? In case you have recommendation to share, soar in.
