I am not really sure what news group this should be posted to. It has to
do
with a visual studio install project for a c# application.
We have noticed that if any of the files installed by the installer are
moved or deleted that this automatically triggers the installer the next
time the application is started.
While this would appropriate if the file in question were an executable, the
files are actually report files. Clients want to be able to choose new
loacations for these files, but cannot do so without causing installer to be
involked. We do not know how this feature got set or how to disable it for
the report files.
Worse yet, if we allow the installer to completion the install fails and the
installer dutifully removes all the install files including the reports.
Can someone give me guidance as to how to fix this?
--
Henry Stock,
onProject.com
hs****@onproject.com
