Hi,
I created a custom action "launch file"
Because I cannot execute the file using system environment variable (is it a bug? http://www.advancedinstaller.com/forums ... =2&t=28826) I entered the exact path.
So now using the exact path I can execute the file I need.
The problem is that the file execution behave differently when I execute it via cmd and when it is being executed via the 'custom action'.
The different behavior is not related to timing because I executed it those on the same time (I added message box before the execution and then tried to execute via cmd and via 'custom action').
For simplicity, the file I'm launching only check if environment variable %NP_APACHE_HOME% is defined.
In case it is not defined it just changed the title and echo it, else it does nothing.
At the end I entered a pause so i can compare the results.
Surprisingly the behavior is different.
I can say for sure that the problem is with evaluating environment variables. My guess it is because of the shell that of the launcher.
It looks like a bug.
Can you please advice?
Thanks.
FOLLOW US
Get the latest news in Application Packaging