Hi Phil,
Thank you for getting back to me,
Yes I have tried doing a registry search then calling that variable within
the InstallCommand for exepackage however it doesn't seem to be able to read
it in that way, even though in the logs I do see the variable being declared
but when the installcommand is executed it is blank where the variable was
suppose to be.
If I hard code a variable it will accept that and works (variable to the
registry search does not work).
Seems a bit of overkill to do a custom action just to set a variable however
I will investigate it. I am completely new to burn and never done a burn
custom action. Is it the same process as a standard custom action?
Reg search:-
<util:RegistrySearch Root ="HKLM" Id="regInstallLocation_64"
Key="Key\Setup" Value="InstallLocation" Result="value"
Variable="[INSTALLDIR]" Win64="yes" />
Installcommand:-
InstallCommand ="/S /D=[INSTALLDIR]"
Variable hard coded:-
<Variable Name="INSTALLDIR" Type="string" Value="C:\Program Files
(x86)\Install" />
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-bundle-EXE-setting-property-tp7595178p7596200.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
