BrowseIIS custom action not working with multiple instances

[AndyL]

We have an installer that uses the BrowseIIS custom action to populate a combo box so the user can select which IIS web site to install to.
Our installer also supports multiple instances.

The BrowseIIS action works fine for the initial installation of the default instance of the application.
If I run the installer again and choose to install a second instance of the application, BrowseIIS seems not to work, and the combo box is empty.

It worked fine in an older version of the installer that we built with AI 20.9. In that version, the available web sites were correctly listed, whether doing a clean install or installing a second instance. The problem seems to have appeared between versions 20.9 and 21.2.2.

[AndyL]

I re-tried this with 22.0, and this seems to be fixed in that version.

I'd like to suggest that IIS configuration should perhaps be a bigger part of regression testing for Advanced Installer. Of the 4 times we've moved to a newer version of Advanced Installer in the past, 3 times the upgrade has broken something, and two of them were to do with IIS. In 19.0 the AI_IIsConfig custom action was broken, and in 21.2 the BrowseIIS custom action was broken.

[Catalin]

Hello Andy,

I'm really sorry to hear that and I apologize for the incoveniences you've faced while upgrading to a newer version of Advanced Installer.

This is definitely not something we are proud of - strange that we hadn't had much (if any) complaints about our IIS support lately.

I have forwarded your feedback to our team and we will try to focus some more resources into the IIS support.

Best regards,
Catalin

[AndyL]

Maybe not many of us are still using it! I guess most people building web applications are deploying to the cloud nowadays and not IIS. But it was the main reason we switched to your product from one of your competitors a few years ago - your support for configuring IIS was leagues ahead of theirs.

[Catalin]

I understand, Andy.

Now that I've forwarded your feedback to our QA team to focus more on this feature, hopefully we will no longer have such issues in the future.

Best regards,
Catalin