We have a program in which the installer checks for the configuration file, and if it exists, it does not copy this file (it is assumed that the user has changed his configuration file and wants to save these changes). Unfortunately, this application is prior to Vista and stores the configuration file in Program Files. The problem is that if you manually destroyed the directory when it reinstalls a specific API, it still thinks that there is a directory there. VB6, for example, and its search in the file dialog box sees a folder, however explorer, cmd shell, etc. Cannot see the folder. Writing the file still leaves the old file (for some APIs, but not for explorer), which cannot be deleted except for the form in the Browse File dialog box.
What happens to these Phantom folders and how do we delete the file so that all the APIs display the same thing? Perhaps this is due to TxF or the search index, but both the installer we use (InnoSetup) and the application parts (parts written in VB6) see the old version of the file, and everything else sees the current version.
source
share