In article <[EMAIL PROTECTED]>,
mscheuner <[EMAIL PROTECTED]> writes:
>
> Thanks for your response, Richard
>
> >>Are you setting the property before the user has a chance to specify
> >>the install location? You need to set the property after any changes
> >>to the install location are made.
>
> I'm trying to store the install location the user has picked into
> "ARPINSTALLLOCATION" using a custom action which gets fired
> "After=InstallFiles" - I would assume by then the proper install directory
> has been picked and set, no??
>
> <CustomAction Id='SAVEINSTALLLOCATION' Property="ARPINSTALLLOCATION"
> Value="[INSTALLDIR]" />
>
> <InstallExecuteSequence>
> <Custom After='InstallFiles' Action='SAVEINSTALLLOCATION' />
> </InstallExecuteSequence>
>
> Do I need to do something when installing a new version in order to *find*
> this install location?
I believe you'll need to set this before the RegisterProduct action,
which takes care of all the Add/Remove Program stuff, but the
documentation isn't explicit on exactly which standard action consumes
this property.
When you run your install, what does the verbose log say when your
action is run? It should have a property change notification in the
log.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
