The update behavior of VS 2008 setup projects uses file update rules, and this means that files updated by the user won't be replaced. This is normally what people want, so that databases and so on don't get completely replaced.

The only way I know of is to modify your MSI file with Orca. In the InstallExecuteSequence table, delete the InstallExecute row (probably at 6500) and change the sequence of RemoveExistingProducts so that it is immediatly after InstallInitialize. This will result in the uninstall of the old product (the RemoveExistingProducts) being done before your files are installed.

Hi TDN,

I assume you mean the User-Scope Application Settings since that Application- Scope Application Settings cannot be set by the users. I don’t think it is good idea to override the User-Scope Application Settings when upgrade an application. The User-Scope Application Settings is set by the end users and provide the users functionalities to custom the application. If you overwrite these settings, these configurations will be lost.

If you still want to overwrite these settings, you can save these setting to an individual file. And this file will be overwritten by default when you upgrade the application.

Hope this helps.
Best regards.
Rong-Chun Zhang

Windows Forms General FAQs
Windows Forms Data Controls and Databinding FAQs

The update behavior of VS 2008 setup projects uses file update rules, and this means that files updated by the user won't be replaced. This is normally what people want, so that databases and so on don't get completely replaced.

The only way I know of is to modify your MSI file with Orca. In the InstallExecuteSequence table, delete the InstallExecute row (probably at 6500) and change the sequence of RemoveExistingProducts so that it is immediatly after InstallInitialize. This will result in the uninstall of the old product (the RemoveExistingProducts) being done before your files are installed.