visual studio .net setup: Hello Again

I have a nother problem with my MSI project.
Lets say Someone installed the application.
when he finished he has at least config 10 files ( all with the same ext.)
he can change them manually at any time.
Now , when I'll give him another MSI (newer version of the file)
for updrage purpose I dont want the Upgrade Delete these config files but
keep using them. but if the new MSI is running at "New Install" mode and not
at "Upgrade mode" it sould create these files.

How can I make this problem work ???

Thanks a lot
Ben

Are you actually seeing a problem.?
Are these configuration files installed via setup or is your application
creating them.

This is how (I remember) this should work.
1. You install version 1
2. You run version 2 with remove previous version set to true
3. Windows Install Removes the previous version, but should leave any
"non-versioned" files that have changed from the original.
4. Any files that were not installed by version 1 should remain.
5. Version 2 should be installed, if the user chooses the same directory
then all should be well (although if version 2 contains a copy of the
config files then I think it depends on the date/time stamps of the files
which one wins)

----------------------------------------------------------------------------
---------------------------------
Patrick Baker - Visual Basic/Deployment Quality Assurance Team
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
[quoted text, click to view]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10
.phx.gbl
[quoted text, click to view]