Is there any to make the IIS configuration optional at install time?
It's not possible to add the IIS configuration to a Feature on the Organization page.
I tried and no matter what Features are chosen at install the IIS configuration is always executed.
Suggested Articles
-
teknohippy
- Posts: 7
- Joined: Mon Jan 23, 2006 5:35 pm
Re: Optional IIS Confiuguration at Install Time
Hi,
Currently Advanced Installer cannot condition the entire IIS configuration. However, this improvement is on our TODO list and it will be available in a future version. Until then, a solution is to use the same condition for all IIS elements in the package (virtual directories, web sites etc.).
Regards,
Cosmin
Currently Advanced Installer cannot condition the entire IIS configuration. However, this improvement is on our TODO list and it will be available in a future version. Until then, a solution is to use the same condition for all IIS elements in the package (virtual directories, web sites etc.).
Regards,
Cosmin
-
teknohippy
- Posts: 7
- Joined: Mon Jan 23, 2006 5:35 pm
Re: Optional IIS Confiuguration at Install Time
Can you briefly outline what you mean by that? Just enough to get me started looking in the right places.
Re: Optional IIS Confiuguration at Install Time
Hi,
The condition of a virtual directory can be set in the "Install Condition" field from the Virtual Directory tab of the IIS page.
The condition of a web site can be set in the "Install Condition" field from the Web Site tab of the IIS page.
The condition of an application pool can be set in the "Install Condition" field from the Application Pool tab of the IIS page.
If all IIS elements have the same condition, the IIS actions are conditioned indirectly. For example, you can condition all your IIS elements with a feature action to indirectly associate them with the feature.
Regards,
Cosmin
The condition of a virtual directory can be set in the "Install Condition" field from the Virtual Directory tab of the IIS page.
The condition of a web site can be set in the "Install Condition" field from the Web Site tab of the IIS page.
The condition of an application pool can be set in the "Install Condition" field from the Application Pool tab of the IIS page.
If all IIS elements have the same condition, the IIS actions are conditioned indirectly. For example, you can condition all your IIS elements with a feature action to indirectly associate them with the feature.
Regards,
Cosmin
Re: Optional IIS Confiuguration at Install Time
Hi,
I built an installer for a big solution with multiple features. One of these features (a webservice) must be installed on a machine with IIS, other features must be installed on a machine with other prerequisites (e.q. sql server).
Additionally I have a common feature (some dlls) with is installed on each machine ("Installed by default" and "Not displayed in feature tree")
I set the installtion behaviour condition of the the webservice feature to IIS_INSTALLED<>"" with install level 0, so this feature is only provided in feature selection tree when the installer runs on a machine with installed IIS.
I also set the conditions of the virtual directory, the app pool and the web site to &WS_FEATURE=3.
Everything is fine so far:
If I run the installer on a machine with IIS, and deselect the WebService feature, then it (the app pool and the web site) will not be installed.
But now I have the following problem:
If I run the installer on a machine without IIS to install the other features, I got an error at install execution stage "This version of IIS is not supported or not installed" (although the WebService feature was not selected [even not provided because of installation behaviour condition] in feature selection tree).
I don't want to break the installer in to separate installers (e.g. beacuse of the common feature) and I don't want to add the prerequisite IIS to the installer (because it would install IIS on machines which doesn't need it to run the system)
Your last post here was from 2009: is it now possible to deactivate the complete IIS step (with contition &WS_FEATURE=3)?
Or when do you plan to release this AdvancedInstaller feature?
Regards, Jogi
I built an installer for a big solution with multiple features. One of these features (a webservice) must be installed on a machine with IIS, other features must be installed on a machine with other prerequisites (e.q. sql server).
Additionally I have a common feature (some dlls) with is installed on each machine ("Installed by default" and "Not displayed in feature tree")
I set the installtion behaviour condition of the the webservice feature to IIS_INSTALLED<>"" with install level 0, so this feature is only provided in feature selection tree when the installer runs on a machine with installed IIS.
I also set the conditions of the virtual directory, the app pool and the web site to &WS_FEATURE=3.
Everything is fine so far:
If I run the installer on a machine with IIS, and deselect the WebService feature, then it (the app pool and the web site) will not be installed.
But now I have the following problem:
If I run the installer on a machine without IIS to install the other features, I got an error at install execution stage "This version of IIS is not supported or not installed" (although the WebService feature was not selected [even not provided because of installation behaviour condition] in feature selection tree).
I don't want to break the installer in to separate installers (e.g. beacuse of the common feature) and I don't want to add the prerequisite IIS to the installer (because it would install IIS on machines which doesn't need it to run the system)
Your last post here was from 2009: is it now possible to deactivate the complete IIS step (with contition &WS_FEATURE=3)?
Or when do you plan to release this AdvancedInstaller feature?
Regards, Jogi
Re: Optional IIS Confiuguration at Install Time
Hello Jogi and welcome to Advanced Installer forums,
Thank you for your interest in Advanced Installer.
Indeed, I can reproduce and confirm this issue. A fix will be available in the next version of Advanced Installer, which will be available soon, in a couple of days. Thank you for bringing it to our attention.
Also, until then if you need this fix you can send us an email to support at advancedinstaller dot com and we can send you a RC containing this fix.
If there is anything I can help with, please let me know.
Best regards,
Dan
Thank you for your interest in Advanced Installer.
Indeed, I can reproduce and confirm this issue. A fix will be available in the next version of Advanced Installer, which will be available soon, in a couple of days. Thank you for bringing it to our attention.
Also, until then if you need this fix you can send us an email to support at advancedinstaller dot com and we can send you a RC containing this fix.
If there is anything I can help with, please let me know.
Best regards,
Dan