I'll probably not use the WiX CAs to install my website (I'm sorely tempted
to!), purely because I'm worried about the possible fragility and don't want
to risk it in a production environment. An alternative method that I've used
is to create a new metabase property, specifically for tracking my web-site.
It works fine (means that users can fiddle with web-site port etc. to their
heart's content, and keeps the web-related info in one place: IIS), although
any minute now I'm expecting someone to tell me how unwittingly evil I am...
:0) If WiX were to follow this approach then only mad metabase-hackers would
be able to ruin things (in which case, good luck to 'em).
Karim
Mike Dimmick-2 wrote:
>
> To add to Rob's extremely terse answer ;) the IIS custom actions use the
> IP
> address/port/Host header tuple to discover the internal website ID for the
> site. Unfortunately there's no special place to store in the metabase that
> the website/virtual directory was installed by WiX - not even a field that
> we can repurpose, because all the fields accessible through the metabase
> API
> are editable in the UI and can therefore be broken by the user.
>
> Windows Installer does not persist values that properties acquire during
> installation. The only thing it remembers is the key path of every
> component
> that's installed, and I'm not sure that it sets the directory properties
> to
> match. Any property whose value can be changed which you rely on during
> maintenance or uninstall must be persisted somehow by you and reloaded
> appropriately.
>
> That said, I think WiX is going to have to bite the bullet here and
> actually
> record the site ID in the registry somewhere. I would propose HKLM/HKCU
> (depending on value of ALLUSERS)\Software\Microsoft\Windows Installer
> XML\Properties\{component GUID} as a suitable location. We might want to
> record the product code as well in case the same website component is
> installed to different locations by different products. While it would be
> nice to use the Registry table to do this, I fear it would cause problems
> with multiple definitions of components (assuming you added the new value
> to
> the same component that contained the website).
>
> I realise this goes against the WiX philosophy of only installing exactly
> what the source says - it's remarkably clean in that respect - but right
> now
> the IIS custom actions seem very fragile.
>
> --
> Mike Dimmick
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Rob
> Mensching
> Sent: 21 December 2007 11:10
> To: Meyrignac, Jean-Charles
> Cc: [email protected]
> Subject: Re: [WiX-users] Uninstall a Website
>
> What is the value for your PORT property during uninstall?
>
> Meyrignac, Jean-Charles wrote:
>>
>> I have a weird bug while uninstalling a website on Windows XP, using
>> the MSI installer: when the application is uninstalled, *IIS is
>> completely* *broken*.
>>
>> Here is the part installing my web site:
>>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> WiX-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
--
View this message in context:
http://www.nabble.com/Uninstall-a-Website-tp14378768p15140981.html
Sent from the wix-users mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
