Hi
I’m using temporary batch and vbs scripts for copying files, as you have suggested in
http://www.advancedinstaller.com/forums ... =2&t=11380.
Unfortunately this approach doesn’t work because of an advanced installer problem with temporary files.
On first installation of a new version (which new product code) the vbs and batch scripts are copied to the temp folder, but unfortunately will be delete from that folder BEFORE my copy-custom-action (which runs on the standard Install-custom action) wants to use them. Consequently the setup produces an error and starts a rollback of installation.
When I restart the same setup after the rollback, everything seems to work right. The batch scripts exist so long in the temp folder that my custom action can use them and copy the files correctly, thus that the setup can finish correctly.
Unfortunately it’s no option to tell our clients that they should run the setup twice for getting it working.
Is this a known problem? Do you have any suggests for a quick resolve of that problem?
By the way: I’m using the newest 8.6 advanced installer version.