We have a service deliverable msi where optionally have some w08/iis70 "Default
Web Site" vdir settings we want to apply and some "Site1 Web Site" and "Site2
Web Site" settings we want to apply (see relevant excerpt below). We need to
allow for deployments where "Site1 Web Site" and "Site2 Web Site" already exist
as a result of OPS having set them up in advance. This is to enable scenarios
where all web sites are advertised on tcp/80 and tcp/443 and OPS uses
environment specific IP or host header name settings to differentiate incoming
requests. In our installer we won't know what those environment specific IP
or host header name settings are.
What we are finding is that the iis:WebSite extension uses iis:WebAddress port
settings to determine if the site is already present. So in cases where all
three iis:WebSite details in our code of iis:WebAddress port=80 defined, and no
other unique setting such as ip or host header, they always end up latching
onto and modifying the "Default Web Site".
q1 - is this expected behavior for the iis:WebSite extension?
q2 - if this is expected behavior is there some way to work around this so that
we can get it looking for an existing install of the iis:WebSite using just the
Name attribute value instead?
q3 - if this is expected behavior is this something that has not previously had
a bug filed against it to get fixed in some post wix3 official beta 3.0.4805.0
release since having iis:WebSite look for existing install of the site using
just the Name attribute value presents a much more powerful story in terms of
service deliverable msi's where you have to be able to install against cases
where the only unique website thing you can know, want to have to know, at
development time is the Name.
<iis:WebAppPool Id="DefaultAppPool" Name="DefaultAppPool" />
<iis:WebSite Id="DefaultWebSite" Description="Default Web Site">
<iis:WebAddress Id="http" Port="80" />
</iis:WebSite>
<Component Id="Site1AppPool" Guid="ACF34F1A-5778-4A98-8AF9-7CF38A81AF6F"
KeyPath="yes" Permanent="yes">
<iis:WebAppPool Id="Site1AppPool" Name="Site1AppPool"
Identity="networkService" />
</Component>
<Component Id="Site1" Guid="35BD9B02-7833-4CCE-9BC6-D8B8B49E5347"
Permanent="yes">
<File Id="InstalledSite1.txt" Name="InstalledSite1.txt"
Source="Resources\InstalledComponent.txt" KeyPath="yes" />
<!-- TODO: copy Site1Dir files into place here -->
<iis:WebSite Id="Site1WebSite" Description="Site1 Web Site"
Directory="Site1Dir">
<iis:WebApplication Id="Site1App" Name="Site1 Application"
WebAppPool="Site1AppPool" Isolation="medium" />
<iis:WebAddress Id="Site1WebAddress" Port="80" />
<iis:WebAddress Id="Site1WebAddressSsl" Port="443" Secure="yes" />
</iis:WebSite>
</Component>
<Component Id="Site2AppPool" Guid="510AD484-C0E6-441D-9E07-8B583D2207CA"
KeyPath="yes" Permanent="yes">
<iis:WebAppPool Id="Site2AppPool" Name="Site2AppPool"
Identity="networkService" />
</Component>
<Component Id="Site2" Guid="AFBE602C-550C-43DB-A36A-BCEC66569967"
Permanent="yes">
<File Id="InstalledSite2.txt" Name="InstalledSite2.txt"
Source="Resources\InstalledComponent.txt" KeyPath="yes" />
<!-- TODO: copy Site2Dir files into place here -->
<iis:WebSite Id="Site2WebSite" Description="Site2 Web Site"
Directory="Site2Dir">
<iis:WebApplication Id="Site2App" Name="Site2 Application"
WebAppPool="Site2AppPool" Isolation="medium" />
<iis:WebAddress Id="Site2WebAddress" Port="80" />
<iis:WebAddress Id="Site2WebAddressSsl" Port="443" Secure="yes" />
</iis:WebSite>
</Component>
Asdf
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
