It would be nice if the Install Conditions for prerequisties were more flexible.
for example We require .NET 2.0 runtime, so in the "Search" stage we check if it is installed and we also check the source directory for the installer. If it isn't installed but the installer is present (as is the case if installing from the CD) then a custom action launches the installer before continuing. However if the installer is not present (downloaded from the website) then we would like the software prerequisite to fire enabling the user to automatically download the installer.
However the prerequisite is appears to be checked prior to the search and any of the custom actions.
Suggested Articles
Hi,
I'm afraid that i don't understand exactly what you are trying to achieve. Please give me more details.
Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
I'm afraid that i don't understand exactly what you are trying to achieve. Please give me more details.
Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
ok, AI has the nifty feature of allowing you to specify software prerequisites a nd have a downloader start up to download the installer if they are not present. This is great but the "Install Conditions" for these prerequisites are not very helpful.
In our situation we need the .NET 2.0 runtime. If the client is installing from a CD, the runtime installer will be present on the CD and I can add a couple of searchs and custom action to install it automatically if not already installed. However if they download the installer from the website it doesn't have the .NET installer (to save on bandwidth) so if it isn't installed already THEN I would like to be able to fire up the downloader tool to grab it and install it.
However the problem is that the Software prerequistes are all evaluated before anything else (as far as I can) and can't even use a custom property to control if it should launch or not.
I would have though the software prerequisites would be evaluated just before the launch conditions and use the same conditions as everything else.
In our situation we need the .NET 2.0 runtime. If the client is installing from a CD, the runtime installer will be present on the CD and I can add a couple of searchs and custom action to install it automatically if not already installed. However if they download the installer from the website it doesn't have the .NET installer (to save on bandwidth) so if it isn't installed already THEN I would like to be able to fire up the downloader tool to grab it and install it.
However the problem is that the Software prerequistes are all evaluated before anything else (as far as I can) and can't even use a custom property to control if it should launch or not.
I would have though the software prerequisites would be evaluated just before the launch conditions and use the same conditions as everything else.
Hi,
You can create a search in the "Search" page with same values used for the prerequisites and use this search property as launch condition for you main package. This is usually done to avoid to launch the package if the user directly click on the msi file.
Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
The Setup.exe tool do the prerequisites job. The prerequisites are all evaluated by the Setup.exe before the package is installed. This is because the prerequisites condition the installation of the main package. To use windows installer property as install condition for a prerequisite is not possible since the main package not runs at this point.However the problem is that the Software prerequistes are all evaluated before anything else (as far as I can) and can't even use a custom property to control if it should launch or not.
I would have though the software prerequisites would be evaluated just before the launch conditions and use the same conditions as everything else.
You can create a search in the "Search" page with same values used for the prerequisites and use this search property as launch condition for you main package. This is usually done to avoid to launch the package if the user directly click on the msi file.
Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com