Hi...
I'm looking to get my installer to appropriately set an entry
in one of those "tricky" environment variables, like %PATH%. By "tricky" I
mean shared and accretive - it's a multi-value crossroads that everybody and
their brother will be mucking with. I want to make sure our addition gets in
there but don't want to just keep appending our root every time the installer
is run. In the same vein, I can't just blank the variable when our product is
uninstalled.
So I was thinking I'd add a custom action type 51 to get the
value into a property and a conditionalized component with a test on the value,
but I'm not quite clear on how all the pieces would fit together... Something
like
<Component Id="SetPath">
<Condition><![CDATA[NOT EnvPath><C:\Program Files\Mypath;]]></Condition>
<Environment Id="EnvSetPath" Action="set" Name="PATH" Part="first"
Permanent="yes" System="yes" Value="C:\Program Files\MyPath" />
</Component>
...
<CustomAction Id="EnvPath" Property="EnvPath" Value="[%PATH]" />
Problem is that all the examples I'm cribbing from are using
ellipsis too, so I'm not sure if I have to declare what phase the custom action
will be executed in, etc.
Am I on the right track?
Thanks
Mark
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
