Filter Feature in all option

[Mir]

Hi,
I have tested your software, and it's realy good. I want to change my software and go to Advanced Installer, but I have question:
Why "Filter Feature" selection and "Move to Feature" is native in all the Resources (File and folders, Registry, Assemblies, Services,..) but is missing in System Changes ( Schedule, Firewall, Group,...) and Server (IIS, SQL Script,...)?
Did you plan to make filter feature so easy in all the software?
I try installing IIS site with "Install condition" but is not so easy like "filter Feature or Move to Feature".
The problem is that I have 2 Website that I want organize in 2 Feature (so the user select the feature to install), I write a condition For first Website "example: ((&MainFeature = 3) AND NOT (!MainFeature = 3)) " and second Website " ((&SecondFeature = 3) AND NOT (!SecondFeature = 3)).
Yet at the first Install all is good (I select the feature and the installer make the job), but at second install (add or remove feature) for adding the second website don’t make the job. Files and Folder are created for the second Website but the Website itself not.
Thanks for Help

[Daniel]

Hello and welcome to Advanced Installer forums,

Thank you for your interest in Advanced Installer.

Why "Filter Feature" selection and "Move to Feature" is native in all the Resources (File and folders, Registry, Assemblies, Services,..) but is missing in System Changes ( Schedule, Firewall, Group,...) and Server (IIS, SQL Script,...)?

This is our default implementation. The items added in "Scheduled Task", "IIS", "SQL Scripts" page, etc. cannot be associated with an installation feature (defined in "Organization" page). This items will be always installed during installation as long as their condition (added in the "Condition" field) is valid at install time.

Did you plan to make filter feature so easy in all the software?

I'm not fully understand what you mean. If you are asking us to add support for including all items added in the above pages ("Scheduled Task", "IIS", "SQL Scripts", etc) into installation features, then currently we don't have any plans regarding this improvement. This is because you can easily condition these items to install based on a feature action or state. However, maybe we'll consider this improvement (make feature selection available over all Advanced Installer application pages) in a future version of Advanced Installer. Thank you for your suggestion.

The problem is that I have 2 Website that I want organize in 2 Feature (so the user select the feature to install), I write a condition For first Website "example: ((&MainFeature = 3) AND NOT (!MainFeature = 3)) " and second Website " ((&SecondFeature = 3) AND NOT (!SecondFeature = 3)).
Yet at the first Install all is good (I select the feature and the installer make the job), but at second install (add or remove feature) for adding the second website don’t make the job. Files and Folder are created for the second Website but the Website itself not.

Please keep in mind this is our default behavior. Our install IIS web sites action (which handles the web sites installation) doesn't run during maintenance mode (e.g. when launching again the setup package and choose change/modify option). Can you please use the approach exposed in "Create IIS entry during Maintenance" thread and see if the behavior still persist?

All the best,
Daniel