NSIS delete function seems to lock files
Hi All,
I'm using NSIS to deliver updates for the product I work on. Just recently I needed to delete a file on the destination machine prior to copying/extracting it from the installer. Although the delete process and copy process seemed to have worked correctly there were issues when it came to using the file later in the installation script.
These are the basic steps(sections) performed:
1. Delete fileX from destination machine
2. Install/extract fileX onto destination machine
3. Execute a function that uses and modifies fileX
* If I run with all 3 steps the 3rd step fails.
* If I manually delete the file and only run steps 2 and 3 the installation works.
* If I put a sleep in between step 1 and 2 the installation works.
I would like to find a better solution to putting a sleep after the delete, also I'm wondering what is actually occuring.
If the NSIS installer is locking the file can it be unlocked?
Has anyone seen something similar to the above scenario?