Ok I have to admit to being wrong, that wasn't at all what I expected
and I am still a bit confused by what I found.
Using a fragment like this and test with v3.0.5120.0:
iis:WebSite Id=WebSite Description=Default Web Site SiteId=*
iis:WebAddress Id=TestWebSite Port=1 /
/iis:WebSite
The
Thanks for the additional details and answers to questions.
I think given iis supports to two web sites using the same name and differing
only in case then it's the right thing to do to have SiteId=* triggered
searching for Description attribute value matches to also be case sensitive.
Wrt our
I think this thread may be misunderstanding what SiteId=* means. I means use
the IIS6 default of setting the site id to the hash of the name, I don't
believe it is triggering a search of the description. A site id of 1 is the
default of the Default Web Site created when IIS is installed. The
In our case we are not so concerned about what SiteId=* will result in wrt
the actual SiteId value that gets generated and used when the msi determines
its necessary to create the iis:WebSite.
What we are really interested in is the fact that including the SiteId=*
attribute, based on
a1 - The iis:WebAddress is required because it is joined to the
iis:WebSite record when the MSI database is queried. WiX does not
currently support a default iis:WebAddress; to be honest, adding one
is simple enough, and would be required if the web site were not found
and you wanted to
I mentioned this because it may catch you out and SiteId=* would fail. For
example, if you created a site that set the site id to a fixed value, something
that is perfectly valid to do (adsutil.vbs does this), the hash matching
wouldn't would. You have found this I believe when trying to find
Hopefully my earlier response will post shortly; this is absolutely
correct for adding new sites, but does not take into account the fact
that SiteId = * does, in fact, trigger a search for the existing site
by description.
Thanks,
Thomas S. Trias
Senior Developer
Artizan Internet Services
I will have to test this because looking at the code I can't see how.
Also, the other poster has suggested that referencing Default Web Site
with SiteId=* didn't work.
Neil
-Original Message-
From: Thomas S. Trias [mailto:tomtr...@artizan.com]
Sent: 09 April 2009 22:25
To: General
Perhaps it depends upon the version of the code? I am developing on top
of 3.0.4923.0. I wouldn't be so adamant, except that I have just
recently been working with the IIS code, and that is the EXACT behavior
I was looking for for the installations and upgrades of our sites, and I
haven't
Thanks for the additional clarification. This is pretty much exactly what we
want and need. The case sensitive Description attribute search would preferably
be case insensitive but this we can live with or file a bug or feature request
against to have changed to be case insensitive
To
10 matches
Mail list logo
