I have a custom action that ends up calling an executable with a large number
of parameters (specifically, the parameters contain fully qualified paths).
This naturally ends up causing the ExeCommand to exceeds its length limit.
<CustomAction
Id="ImportConfiguration"
Directory="ConfigurationFolder"
ExeCommand="..."
Return="check" />
What is the best (or recommended) way of handling the scenario where you
*cannot* reduce the length of the string directly? Do you generate a .cmd on
the fly and execute it that way? Do you move it as proper C# custom action and
run with the Process object?
Thanks,
Navid
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
