Re: [WiX-users] We are getting some unexpected and undesirable behavior from iis:WebAppPool and iis:WebSite extensions, just checking to see if we are doing something wrong.

Thanks for responses. 1. setting the SKIPCONFIGUREIIS property via an immediate CA (scheduled prior to ConfigureIIs of course) to simply skip IIS configuration when the target host already has the website installed would require us having some way to determine if the target host already

Re: [WiX-users] We are getting some unexpected and undesirable behavior from iis:WebAppPool and iis:WebSite extensions, just checking to see if we are doing something wrong.

Setting the SKIPCONFIGUREIIS property via an immediate CA (scheduled prior to ConfigureIIs of course) to simply skip IIS configuration when the target host already has the website installed would require us having some way to determine if the target host already has the website installed

Re: [WiX-users] We are getting some unexpected and undesirable behavior from iis:WebAppPool and iis:WebSite extensions, just checking to see if we are doing something wrong.

The condition for ConfigureIIs (the scheduling CA) is: NOT SKIPCONFIGUREIIS AND VersionNT 400 You could set the SKIPCONFIGUREIIS property via an immediate CA (scheduled prior to ConfigureIIs of course) to simply skip IIS configuration when the target host already has the website installed.

Re: [WiX-users] We are getting some unexpected and undesirable behavior from iis:WebAppPool and iis:WebSite extensions, just checking to see if we are doing something wrong.

Also, WebSite has a ConfigureIfExists property. AppPool though probably always sets its settings so Alex's suggestion below may be the nuke you need. Alex Cater wrote: The condition for ConfigureIIs (the scheduling CA) is: NOT SKIPCONFIGUREIIS AND VersionNT 400 You could set the