d be after TARGETDIR is set, and I'd condition it on Not Installed.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alexander
Gnauck
Sent: Friday, September 22, 2006 2:33 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] propertie
Alexander Gnauck wrote:
> Is there a way to do this with "standard" Wix commands,
> or only with a custom action and a native dll.
>
Write the values using RegistryKey/RegistryValue elements and load them
using RegistrySearch.
--
sig://boB
http://bobs.org
--
Wilson, Phil wrote:
> The standard way to persist that ("the main application directory") is
> to use a type 51 custom action and set the ARPINSTALLLOCATION property,
> then it will get persisted in the MSI way (meaning that
> MsiGetProductInfo with INSTALLPROPERTY_INSTALLLOCATION and other
> stand
The standard way to persist that ("the main application directory") is
to use a type 51 custom action and set the ARPINSTALLLOCATION property,
then it will get persisted in the MSI way (meaning that
MsiGetProductInfo with INSTALLPROPERTY_INSTALLLOCATION and other
standard APIs can get it).
Phil W
sday, September 21, 2006 6:24 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] properties form previous versions
Hello David,
> I use the element of the to retrieve
> previous user-selected property values on uninstalls. I think you
> could do the same thing for up
Hello David,
> I use the element of the to retrieve previous
> user-selected property values on uninstalls. I think you could do the same
> thing for updates.
>
>
> Type="raw"
>Key="SOFTWARE\YourCompany\YourSection\YourKey"
> />
>
>
> In this case, the p
Alex:
I use the element of the to retrieve previous
user-selected property values on uninstalls. I think you could do the same
thing for updates.
In this case, the property value is retreived from the registry if found.
If the key is not found in the registry, then the property val
7 matches
Mail list logo
