Forum Discussion
Exe file working directory
Hi Bogdan,
Thanks for your reply. We have an Archtecture license from Advanced Installer. I am using v15.5. I already tried it the way shown in the video but for some reason that doesn't work. When I follow the steps it starts running the application. The application starts in Advanced Installer (Trace apps) but not when I create the MSIX and run it after installing the MSIX, so that is different. I would expect that these two situation should give the same result. And when I am in the application it cannot be closed because it cannot write an ini file. Only way closing it is to kill the process and then Advanced Installer doesn't continue the fixing for some reason.
Now I have followed the instruction in https://docs.microsoft.com/nl-nl/windows/uwp/porting/package-support-framework . Then I get the working directory done but not the redirection unfortunately so closing the app normally doesn't work.
Hi Rob,
I think I understand what is happening with your app, seems like a bug in our tracing support that practically hides the working dir issue.
To trace the app we include our launcher in the package, and it seems that the launcher is incorrectly setting the working dir for your app. Since in your case, we already know you need to fix this, go to Application Details view from your project and set the "Working Directory" field to the folder where your EXE is located, as you can see in the attached image.
This option is in a different page in Advanced Installer because we started fixing this working dir problem long before the package support framework was announced by MSFT.
Now, that you have set the working dir in Application Details view this problem should be gone, so it remains to see how we fix the second issue, with the file write problem. Maybe you can send me the app so we can reproduce it.
When you try to close the app and the file write operation fails, isn't the error visible and highlighted in the log as in our demo video? If it is you could apply the fix and save the project and only afterwards kill the process.
Another solution is to directly add the file redirection fixup using our toolbar options, without tracing the app, as we already know the problem is with specific file. Our default is to redirect .log files, but you can edit that extension to match your specific file type.