Here's the scenario: I have a product that has a few different applications. One of the applications is a web app. It obviously depends on IIS being installed, however, it is possible to install the other applications without installing the web app.
I don't want the whole package to have a launch condition on IIS, because it's possible to install just the non-web apps on a server. I'd still like to either disable the web application component, or show an error if someone tries to install it and IIS is not installed though.
Is this possible?
Suggested Articles
Re: Making a launch condition for a specific component?
Hi,
You can try this approach:
- use searches to determine if IIS is installed or not; you can search for "inetinfo.exe" and "w3wp.exe" in "[SystemFolder]inetsrv" folder
- create a custom action which evaluates the search properties (if the IIS files were found)
- if both properties are empty, your custom action can show a message box and return 1602 to stop the installation
- this custom action can be conditioned with the IIS web application feature
Please note that only VBScript and Win32 DLL custom actions can have custom return codes.
Regards,
Cosmin
You can try this approach:
- use searches to determine if IIS is installed or not; you can search for "inetinfo.exe" and "w3wp.exe" in "[SystemFolder]inetsrv" folder
- create a custom action which evaluates the search properties (if the IIS files were found)
- if both properties are empty, your custom action can show a message box and return 1602 to stop the installation
- this custom action can be conditioned with the IIS web application feature
Please note that only VBScript and Win32 DLL custom actions can have custom return codes.
Regards,
Cosmin