I have a setup project in which I have a custom action that is adding the target folder to the path. Nothing special, works ok, adds it to the path.
However if I then open a cmd window it's not available. If I psexec and try to directly run something that is in the folder it isn't found.
I logged off the box and on again and it turned up in the cmd echo %PATH% command however this isn't really an option in production.
I will probably be installing the msi via psexec and then I want to then make a second call using something in that folder.
so
psexec \machine-name msiexec /I setup.msi /qn psexec \machine-name exeinabovemsi
Is there something I need to do to flush the path out, it is in the "My Computer -> Properties -> Advanced -> Environment Variables -> Path" list as soon as the msi has installed, just doesn't turn up in the new cmd windows etc.
Thanks
Alan