Hello Krishna,
First of all, thanks for the provided files.
After further investigating this on our end, this seems indeed to be cause by a bug in our application. The root cause of this problem relies in the fact that the
"Wait for custom action to finish before proceeding" flag (
"Custom Actions" page --> your custom action -->
"Execution Options" section) is ignored for our predefined PowerShell custom actions.
As a workaround, we can proceed as it follows: we will have a .BAT file which will launch the powershell.exe process, which will them launch our script into execution. The .BAT file content will be as it follows:
Code: Select all
powershell.exe -ExecutionPolicy Bypass -File "C:\Temp\SoftwareInstall.ps1"
After creating the .BAT file, it is time to add it in your project (in
"Files and Folders" page). After doing so, let's create the custom action that will launch our .BAT file. To do so, please go to
"Custom Actions" page and add a
"Launch File" custom action with sequence. The custom action should look something as it follows:

- CA.PNG (54.33 KiB) Viewed 20603 times
In what regards the bug, I will let you know by updating this thread as soon as it will be fixed. Unfortunately, as for this moment, I am afraid I can not give you any ETA on when this will be fixed.
Hope this helps.
All the best,
Catalin
FOLLOW US
Get the latest news in Application Packaging