You are correct, the Metabase Id is the ultimate thing that defines a web site.
Unfortunately, that identifier is not stable from machine to machine (or
necessarily from install to install). You cannot safely declare that your
WebSite will always install at any Metabase Id #. ServerBindings are supposed
to be the one-to-one mapping to the Metabase Id.
From: Aaron Shurts [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 06, 2007 8:02 AM
To: Rob Mensching
Cc: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Creation of Virtual Directory within existing Website
Rob,
I believe so. The way we install our website is we stop the default site and
add our site in a different ID. When we uninstall, we restart the default site
and restore the original metabase configuration before the install of our
product. Wouldn't it make more sense to be able to specify a site ID for an
existing website? A user could just as easily modify the IP:Port:Header as
they could the description. For example our site *usually* installs to site ID
67 when it is available. So, specifying either 67 or lm/w3svc/67/ROOT would
seem the most reliable as opposed to description or the ServerBindings
property. I haven't looked at the code but it would seem you are enum'ing the
sites until you find the ServerBindings you are looking for. What if I tell
you, hey this is the site ID I want to use...for installs as well, being able
to specify the site ID would be nice. :-)
Regards,
//aj
On 6/6/07, Rob Mensching <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
Does this only happen if there are two web sites with the same IP:Port:Header?
From: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> [mailto:[EMAIL
PROTECTED]<mailto:[EMAIL PROTECTED]>] On Behalf Of Aaron Shurts
Sent: Tuesday, June 05, 2007 12:53 PM
To: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>
Cc: wix-users@lists.sourceforge.net<mailto:wix-users@lists.sourceforge.net>
Subject: Re: [WiX-users] Creation of Virtual Directory within existing Website
Created a bug:
http://sourceforge.net/tracker/index.php?func=detail&aid=1731648&group_id=105970&atid=642714
[ wix-Bugs-1731648 ] Problem referencing existing website to create vDir
Regards,
//aj
On 6/5/07, Aaron Shurts < [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
I have done many experiments trying to get this to work, but keep coming up
with the same problems. I tried creating a dummy component with the website
info and referencing that, same result. I tried actually nesting underneath a
component with the website settings and the ConfigureIfExists flag set to 'no'
and still same result. No matter what I do, the virtual directory always ends
up under the default stopped website, rather than my started website. It looks
like I might have to whip up a quick VBScript custom action in the mean time to
get this accomplished. I'll go ahead and create a bug for this.
Regards,
//aj
On 6/5/07, Aaron Shurts < [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
I am having the same problem, so if anyone has a solution, please let us know
what it might be.
Regards,
//aj
On 6/4/07, [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> <[EMAIL
PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
The scenario is that my target machine has two websites as follows:
Default Web Site, IP Address - All Unassigned, Port - 80, Status (STOPPED)
My Website, IP Address - All Unassigned, Port - 80, Status (STARTED)
Therefore they are identical but the default site is stopped (I know that the
default web site should probably be deleted but this is not within my control).
I am attempting to create a new virtual directory within My Website and
therefore I reference it as follows:
<!-- Reference to website -->
<WebSite Id='MyWebSite' Description='My Website'>
<WebAddress Id='MyWebsiteAddr' Port='80' />
</WebSite>
The problem I am having is that my virtual is always created within the default
web site. If I change the Port or IP Address of the default web site then it is
created within my website as expected (but this is not something I can do in
production). Therefore the behaviour seems to be that the website lookup is
done using IP Address and Port only (i.e. Description is ignored), and that the
first IIS web site found that matches will be used (Default Web Site in this
case as it is instance 1).
Is there a way to do a more exact match to ensure that my virtual is always
created within the correct website.
As always any feedback would be most appreciated.
One thing I should mention here is that I have only tested this on XP (using
IISAdmin.Net to replicate sites), I have not yet tested on 2003
.
--------------------------------------------------------------------------------------------------------------------
HBOS plc, Registered in Scotland No. SC218813. Registered Office: The Mound,
Edinburgh EH1 1YZ. HBOS plc is a holding company, subsidiaries of which are
authorised and regulated by the Financial Services Authority.
==============================================================================
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net<mailto:WiX-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
