D
DonutMan
I have a setup project that I've created for an application that
requires a temporary data file to be installed in the root
installation directory. On application startup, if this data file
exists in the directory, the application will process the file and
then rename it so that it does not get processed again the next time
the application is run. In this manner, data updates are accomplished
by simply copying a new data file into the installation directory
instead of having to reinstall the application.
The problem, of course, is that when the application is launched, the
Windows Installer mechanism automatically detects that the data file
is missing and restores the file before actually starting the
application. Does anyone know the best way to prevent this from
occurring? Will this happen if I install the data file to a different
location instead (e.g., the "My Documents" folder?)
Thanks in advance,
Mike
requires a temporary data file to be installed in the root
installation directory. On application startup, if this data file
exists in the directory, the application will process the file and
then rename it so that it does not get processed again the next time
the application is run. In this manner, data updates are accomplished
by simply copying a new data file into the installation directory
instead of having to reinstall the application.
The problem, of course, is that when the application is launched, the
Windows Installer mechanism automatically detects that the data file
is missing and restores the file before actually starting the
application. Does anyone know the best way to prevent this from
occurring? Will this happen if I install the data file to a different
location instead (e.g., the "My Documents" folder?)
Thanks in advance,
Mike