Hi James,
I'd like to choose the identifier... If it is already in use, then notify the user "it is in use, do you want to proceed?" and allow them to choose a new identifier and change it to that number. That way, if they are installing 6 new sites, they could make the new identifier 500 or something to avoid a conflict. I see this as a necessity when using the msi to create web services, or WCF farms of servers - where there are dozens of websites to install.
Thank you for your suggestion. We will implement this in a future version of Advanced Installer.
Something else, and maybe I am missing it, would it be possible to remove sites that may exist? For example, when the IIS config runs, if the "Default Web Site" exists, delete it at run time.
We are reluctant to implement this feature as uninstalling software other than the one installed by the same package is not a generally a good practice. However we may consider implementing this in the future, with the addition that the user will be prompted whether or not he wants to uninstall the said website.
Do you all have an ETA of a version when some of these things will be implemented? Most concerned about doing multiple ports, ie 80 & 443, on sites that are going to use a certificate.
I am afraid we can not offer you an ETA. We can only assure you that SSL is a top priority on our list of IIS features.
Please feel free to offer us any other suggestions that might offer everyone a better Advanced Installer experience.
Best regards,
Gabriel
FOLLOW US
Get the latest news in Application Packaging