It's a good idea, but I don't think that's it, because I did clear everything
down, several times and try again. In other words I uninstalled, the file was
removed, I re-installed using the "permanent" property and uninstalled and
the file was still removed. I tried this several times and rechecked I had
the permanent property set as it was not what I was expecting.
I can only say that I did add and remove various outputs, files, .exe and
dll's to the applications folder while trying to understand how setup
projects work. It was only when I cleared down the setup project and started
again that it worked. Now of course I can't reproduce the problem, but then I
don't want to
The trouble is I was trying to get the system to do what I thought it should
do and I wasn't trying to record what I was doing in order to reproduce it,
so I can't be absolutely clear.
"Family Tree Mike" wrote:
Quote:
> Is it possible the file was installed with a setup where you had marked it as
> not being permanent, but then ran your new installer to try and uninstall it?
> If this is the case, the permanancy of the file had already been set. This
> would explain why your later new build worked.
>
> "flutophilus" wrote:
> Quote:
> > Hi Steven,
> >
> > I created a test project as you suggested and it worked fine. I did wonder
> > if the problem was becuase the file I was marking permanent was the config
> > file (MyApp.exe.config) which is, I realised already included as part of the
> > primary output from the main project. But it worked OK on this file, which is
> > great.
> >
> > So I went back to my original project and removed and re-added the primary
> > output and the config file separately, marked the coinfig file as permanent
> > and to my great pleasure it worked !!! So I have no idea why it failed to
> > wrok before.
> >
> > Now when I uninstal it leaves the config file behind.
> >
> > Interestingly if I re-instal into the same location it does not overwrite
> > the config file. This is great but is it the expected behaviour ? Can I rely
> > on it?
> >
> > Cheers
> >
> >
> >
> > ""Steven Cheng"" wrote:
> > Quote:
> > > Hi flutophilus,
> > >
> > > From your description, I understand you've built a setup project which set
> > > a certain file to "permanent = true" so as to prevent it from being removed
> > > at uninstall time, however, you found the file still got removed, correct?
> > >
> > > I agree that the "permanent=true" should keep the file from being removed
> > > as you expected. I've also performed some simple tests by creating some
> > > setup project and set some files(deploy to program files or desktop folder)
> > > to "permanent =true", and they're preserved as expected after I uninstall
> > > the program. Therefore, I think this should be a specific case. Have you
> > > tried a simple setup (or try mark other files to permanent) to see whether
> > > you can get the expected behavior. Also, is there other custom code module
> > > in setup project that may touch the file?
> > >
> > > Sincerely,
> > >
> > > Steven Cheng
> > >
> > > Microsoft MSDN Online Support Lead
> > >
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > >
> > >
> > > --------------------
> > > >From: =?Utf-8?B?Zmx1dG9waGlsdXM=?= <flutophilus@xxxxxx>
> > > >Subject: VS2005 Setup Project File with Property 'Permanent' is uninstalled
> > > >Date: Wed, 5 Mar 2008 07:39:05 -0800
> > >
> > > >
> > > >Hi,
> > > >
> > > >I'm working with VS2005 and I have a setup project that installs a Windows
> > > >forms application. I have a config file ( it's the app.config file -
> > > >MyApp.exe.config) which I want to leave on the target system if the
> > > >application is uninstalled. In the Setup Project File System designer I
> > > set
> > > >the "permanent" property of this file to "True", which should leave the
> > > file
> > > >installed if the user uninstalls the application. However if I uninstall
> > > the
> > > >application using the setup.exe generated by the setup project it removes
> > > >this file.
> > > >
> > > >Am I doing something wrong?
> > > >
> > > >
> > >
> > >