title: Granular control with WIX IIS website installation
body: <p>I am authoring an installer that creates a new website and application pool. This installer is for internal use within several development environments which all have subtle differences. One may use only HTTP, another only HTTPS and one might use both. One might use the default <code>ApplicationPoolIdentity</code> identity where as another may use an explicit <code>User</code> reference.</p>
  
  <p>Given the association of a <code>WebAppPool</code> is by ID through a <code>WebApplication</code> which must be nested under a <code>WebSite</code>, each time an option is desired on the installer, the breakout and duplication of features gets ridiculous.</p>
  
  <p>I imagine I am not the first to encounter this, how does one accomplish this much flexibility within an installer?</p>