I have made a custom action to update a xml file which is installed. I'm
passing the path of the file to the custom action with CustomActionData.
This works fine, but when I try to open the xml file in the custom action
the action is looking in the wrong directory.
<CustomAction Id="UpdateConfigCustomAction" BinaryKey="CustomActionsDLL"
DllEntry="UpdateConfigFileAction" Execute="deferred" Return="check"
Impersonate="no" />
<InstallExecuteSequence>
<Custom Action="SetPropertiesCustomAction"
Before="UpdateConfigCustomAction" />
<Custom Action="UpdateConfigCustomAction" Before="InstallFinalize">NOT
Installed</Custom>
</InstallExecuteSequence>
For example the path of the xml file is: C:\Program
Files(x86)\MyProgram\file.xml but the action is looking at
C:\Windows\Installer\****.TMP\C:\Program Files(x86)\MyProgram\file.xml
If I debug the custom action the value of the string is 'C:\Program
Files(x86)\MyProgram\file.xml' but when opening the xml file with for
example the XDocument.Load method the path is prefixed with
C:\Windows\Installer\***.TMP\
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
