Minimum Launch Condition - Advanced Installer Community
prerak6962
Posts: 112
Joined: Mon Dec 08, 2014 5:26 pm

Minimum Launch Condition

Hello,

I have an installer for an ASP.NET web application. The application requires minimum .NET Framework 4.0 and minimum IIS 8.0 for running.
So, I added these two in the "Launch Conditions -> Software" tab.
Untitled.png
Untitled.png (25.11 KiB) Viewed 4077 times
And in case they are not present on the user's machine, I have added them under "Prerequisites" tab under "Pre-install" phase.
The correct image is the one at the end of this post. The below image is getting repeated on its own.
Untitled.png
Untitled.png (25.11 KiB) Viewed 4077 times
But when I run the installer on a test machines, it fails saying that the "product cannot be installed on systems with Internet Information Services version lower than 8.0". But I have IIS version 10 installed on the test machine.

So as per my understanding, it is checking the launch conditions first and in the Advanced Installer version 13.5, the option "Minimum" is missing from the "Launch Conditions" tab as documented here.

So is there anything that I am missing from my side?

Thank you
Prerak
Attachments
Untitled1.png
Untitled1.png (11.07 KiB) Viewed 4077 times
prerak6962
Posts: 112
Joined: Mon Dec 08, 2014 5:26 pm

Re: Minimum Launch Condition

I created a new ASP.NET project and selected the dependencies in the wizard. The behaviour mentioned above can be reproduced in it.
I have attached the .aip file of it here.

Also, for IIS dependency, the default registry search created by the wizard is

Code: Select all

HKLM\SOFTWARE\Microsoft\IISExpress\8.0\Version
But the "Version" value is present at this key in the registry:

Code: Select all

HKLM\SOFTWARE\Microsoft\IISExpress\
So I just updated this under "Prerequisites -> IIS Express 8.0 x64" -> Install Conditions".
If you could update this default registry search to the correct one in the next update, it would be great.

And, am I missing something or misunderstanding something on my part for the above mentioned bizarre behaviour?

Prerak
Attachments
setup.aip
(30.03 KiB) Downloaded 456 times
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Minimum Launch Condition

Hello Prerak,

I'm not sure why this happens. I've tested your sample on a Windows 10 machine with IIS 10 installed and no launch condition was triggered. Can you please re-enable the IIS feature on your test machine and test this again? Maybe some IIS resources were corrupted on your test machine.

To detect the current installed IIS version on target machine we check the version of the following file:

Code: Select all

 %WINDIR%\system32\inetsrv\w3wp.exe
Also, as a side note, please not that it is redundant to add prerequisites in your setup project for the same software for which you also defined launch conditions. When you setup package has a dependency (i.e. IIS) you should either add this as a launch condition or as a prerequisite.

When IIS is added as a launch condition the setup package checks on target machine if IIS is installed and if not cancel the installation and informs the user to manually install it. When IIS is added as a prerequisite the setup package will install the IIS feature if it is not already installed. So, if you want the IIS be installed by the user you should add it as a LC, otherwise if you want it be installed by your setup package you should add it as a prerequisite.

Let us know if this helped.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”