My scenario:
I have 32bit files and 64bit files divided up into 32bit features (only included in my 32bit build) and 64bit features (only included in my 64bit build). This is also true for my IIS website files. This means I need to create two websites (32bit and 64bit) and two application pools (32bit and 64bit) in the IIS view. I set the “Install Condition” field for the websites and application pools so that the correct website and application pool is installed (ex: if it’s a 32bit build, the 32bit website/app pool is installed).

This seems to work for everything, except when I add a “FastCgiModule” mapping to both the 32bit and 64bit websites (only showing 32bit below):

Doing this adds these files to the Global Settings under “FastCGI Settings”:

The issue here is, these FastCgi Settings are no longer conditional. Meaning, both “phpcgi.exe” and “phpcgi.exe_1” will try to be added to IIS, but only one will exist during runtime (either the 32bit one or the 64bit). This causes the installer to fail. I’m guessing this issue will occur to any setting that is added under the “Global Settings”.
So, to work around this, I decided to try and make these settings using “Custom Properties”, since I think these settings will remain conditional (based on the install condition of the website). The problem here is, I cannot get the “isapiCgiRestriction” and “fastCgi” settings to work:

These two settings cause a failure during the IIS configuration part of the install. The “handlers” setting seems to work fine. The only difference I see, is “isapiCgiRestriction” and “fastCgi” are not shown in the AI ui:

So, I’m not sure if AI supports these two custom properties? But, if I manually type in “system.webServer/security/isapiCgiRestriction”, AI seems to detect the collection just fine.
Any suggestions on how I should handle this scenario?
Also, I noticed the following:

This is what my “ISAPI and CGI Restrictions” setting looks like after installation. Notice the “|” symbol at the end of the first entry (which is a “FastCgiModule”). For some reason, AI is appending the pipe symbol to the end of the path. Not sure if this is expected (as a delimiter or something), or if it’s a bug. This occurs when using the built in AI IIS settings (i.e., not using “Custom Properties”).
Thanks.
FOLLOW US
Get the latest news in Application Packaging