You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LaunchTarget could fail because working folder could be changed even when launching a full path exe, etc. Because the launched target could depend in some local config file etc.
The working dir could not be always current dir on launching a target. So, why not add another variable like:
<WixVariable Name="LaunchWorkingFolder"... />
Optional. The address of a null-terminated string that specifies the name of the working directory. If this member is NULL, the current directory is used as the working directory.
"We are failing to execute a wizard after install because it depends on a
find files in the path, and the ShellExecuteEx cannot guarantee per si the
last current folder set."
Unless you set as a parameter when call ShellExecuteEx .
LaunchTarget could fail because working folder could be changed even when launching a full path exe, etc. Because the launched target could depend in some local config file etc.
The working dir could not be always current dir on launching a target. So, why not add another variable like:
<WixVariable Name="LaunchWorkingFolder"... />
Optional. The address of a null-terminated string that specifies the name of the working directory. If this member is NULL, the current directory is used as the working directory.
"We are failing to execute a wizard after install because it depends on a
find files in the path, and the ShellExecuteEx cannot guarantee per si the
last current folder set."
Unless you set as a parameter when call ShellExecuteEx .
This will resolve duplicate with
https://sourceforge.net/tracker/index.php?func=detail&aid=3561299&group_id=105970&atid=642714
The text was updated successfully, but these errors were encountered: