Replies: 1 comment
-
<Product ......................................................
When Impersonate="no" is set, the custom action runs with elevated privileges, which is necessary for actions that require administrative rights, such as modifying system files or registry settings.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm facing an issue with my Wix installer where I want to run a dependent executable (VivePro2OfflineInstall.exe) during the installation of my main application. I have added a custom action to execute the EXE after the installation files are copied, but it doesn't seem to be working. The EXE does not start, and there is no indication that the custom action is being executed. Here is the text file containing relevant portion of my Wix code:
CodeSnippet.txt
I've ensured that the EXE file is included in the installation and is located in the INSTALLFOLDER. I also tried adding logging to debug, but it didn’t help. I suspect there might be an issue with how I'm scheduling the custom action or resolving the directory.
Could someone please help me figure out why the custom action to run the EXE is not working? Any advice or pointers would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions