This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Can't set working directory of an Execute Command Action?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 09, 2012
10:11 AM
Can't set working directory of an Execute Command Action?
Hey folks, just wondering if there is something I'm missing. There are some utilities, like the mysql daemon for example, that require they be executed in a certain directory. This is bad practice of course, but anyhooo ...
Install Anywhere (unlike install4j or InstallBulder) doesn't seem to allow the setting of a working directory for any of it's actions. I'm trying to use the Execute Command Action for this.
Am I missing this in the UI somewhere?
I know I can do it by wrapping it in custom code and setting the working directory in a Java ProcessBuilder object, or wrapping it in a platform specific script, but I'd really rather not have to write custom code for this in my evaluation of these products.
Install Anywhere (unlike install4j or InstallBulder) doesn't seem to allow the setting of a working directory for any of it's actions. I'm trying to use the Execute Command Action for this.
Am I missing this in the UI somewhere?
I know I can do it by wrapping it in custom code and setting the working directory in a Java ProcessBuilder object, or wrapping it in a platform specific script, but I'd really rather not have to write custom code for this in my evaluation of these products.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 12, 2012
01:26 PM
Hi frank2oh,
This is mainly because Installanywhere first extracts itself into the temp and all its execution takes place w.r.t the temp directory where it extracts itself to.
This is true in case of most of the actions in Installanywhere.
Changing the the temp location to the current directory of your program under execution should resolve your issue.
Hope this helps.
Thanks,
Madhav Pai
This is mainly because Installanywhere first extracts itself into the temp and all its execution takes place w.r.t the temp directory where it extracts itself to.
This is true in case of most of the actions in Installanywhere.
Changing the the temp location to the current directory of your program under execution should resolve your issue.
Hope this helps.
Thanks,
Madhav Pai
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)