Please help me! I am incredibly frustrated.
I had a package that was working just fine a few days ago. I have a custom action set to run, and it's a simple VBS script that deletes leftover registry keys. The script works fine when run outside of the installation package.
Today, I made a change to the EULA and product code, and tried to run through the installer, and suddenly it wasn't able to complete and I got the message "A script required for this installation cannot be found". I verified that the VBS script works, changed some text in the dialog it displays, and recompiled the MSI. IT CONTINUED TO RUN THE OLDER VERSION OF THE VBS FILE. I deleted the custom actions, looked in the AIP file to see if there were any references to VBS files (there weren't), and recompiled again. It is still running the old VBS! I can't imagine where it is coming from. I am pulling my hair out. Does anyone have any ideas? I need this to work because the update I made to my software is crucial, and right now I can't send out the update.
Thanks,
Doug
FOLLOW US
Get the latest news in Application Packaging