Thanks for your reply,
Yes, actually in my test, I explicitly include all the files(of the certain
project into my setup project) so that I can set the "permanent" property
for the config file. I think you can rely on it (since the "permanent"
property is expected to behave like this). However, I suggest you
explicitly include the config file into your setup project and set its
permanent property.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we
can improve the support we provide to you. Please feel free to let my
manager know what you think of
the level of service provided. You can send feedback directly to my manager
at: msdnmg@xxxxxx.
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Quote:
>From: =?Utf-8?B?Zmx1dG9waGlsdXM=?= <flutophilus@xxxxxx>
>References: <4EB8D294-DC8E-4411-B4DC-DA2C8D859E48@xxxxxx>
<50V5iUzfIHA.4200@xxxxxx>
Quote:
>Subject: RE: VS2005 Setup Project File with Property 'Permanent' is uninsta
>Date: Thu, 6 Mar 2008 03:44:01 -0800
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
Quote:
>primary output from the main project. But it worked OK on this file, which
is
Quote:
>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
Quote:
>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
Quote:
>on it?
>
>Cheers
>
>
>
>""Steven Cheng"" wrote:
> Quote:
>> Hi flutophilus,
>>
>> From your description, I understand you've built a setup project which
set
Quote:
Quote:
>> a certain file to "permanent = true" so as to prevent it from being
removed
Quote:
Quote:
>> at uninstall time, however, you found the file still got removed,
correct?
Quote:
Quote:
>>
>> I agree that the "permanent=true" should keep the file from being
removed
Quote:
Quote:
>> 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)
Quote:
Quote:
>> to "permanent =true", and they're preserved as expected after I
uninstall
Quote:
Quote:
>> the program. Therefore, I think this should be a specific case. Have
you
Quote:
Quote:
>> tried a simple setup (or try mark other files to permanent) to see
whether
Quote:
Quote:
>> you can get the expected behavior. Also, is there other custom code
module
Quote:
Quote:
>> 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.
Quote:
Quote:
>>
>>
>> -------------------- Quote:
>> >From: =?Utf-8?B?Zmx1dG9waGlsdXM=?= <flutophilus@xxxxxx>
>> >Subject: VS2005 Setup Project File with Property 'Permanent' is
uninstalled
Quote:
Quote:
Quote:
>> >Date: Wed, 5 Mar 2008 07:39:05 -0800
>> Quote:
>> >
>> >Hi,
>> >
>> >I'm working with VS2005 and I have a setup project that installs a
Windows
Quote:
Quote:
Quote:
>> >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 Quote:
>> >the "permanent" property of this file to "True", which should leave the
>> file Quote:
>> >installed if the user uninstalls the application. However if I
uninstall
Quote:
Quote:
>> the Quote:
>> >application using the setup.exe generated by the setup project it
removes
Quote:
Quote:
Quote:
>> >this file.
>> >
>> >Am I doing something wrong?
>> >
>> >
>>
>> >