Solved it...
I created a customaction to populate a property with the powershell folder
<CustomAction Id="CA_Set_PowerShellx86_Path" Directory="POWERSHELLX86_DIR"
Value="[POWERSHELLPATH_X86]"/>
<CustomAction Id="CA_Set_PowerShellx64_Path"
Directory="POWERSHELLX64_DIR" Value="[POWERSHELLPATH_X64]"/>
I use the Directory "property" Directory="POWERSHELLX86_DIR" as the
directory for the component...
Sigh..
Steve
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Can-t-compile-Install-getting-ICE30-error-tp7589530p7589532.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
