Persistent settings

[John]

Hi

I need to store the path to db in my app. I have used app setting for this.
Unfortunately various clients have different db paths and I have set them up
once on each client location. The problem is that when I send them updates
and they uninstall the old version and reinstall the new version the setting
is reset to my settings. This is because the old configuration file is
deleted and replaced by the new one included in the app. Is there a way to
have a setting that is not overwritten by an application reinstall?

Thanks

Regards

[=?Utf-8?B?VG9tIEdhcnRo?=]

John,

See SaveSetting and GetSetting. It's extremely easy to use and saves values
to the HKEY_CurrentUser area of the registry. Uninstalling or reinstalling an
application does not remove the information.

--
Tom Garth
"John" wrote:

Hi

I need to store the path to db in my app. I have used app setting for this.
Unfortunately various clients have different db paths and I have set them up
once on each client location. The problem is that when I send them updates
and they uninstall the old version and reinstall the new version the setting
is reset to my settings. This is because the old configuration file is
deleted and replaced by the new one included in the app. Is there a way to
have a setting that is not overwritten by an application reinstall?

Thanks

Regards

[Mr. Arnold]

"John" <Jo**@nospam.infovis.co.ukwrote in message
news:Oq**************@TK2MSFTNGP03.phx.gbl...

Hi

I need to store the path to db in my app. I have used app setting for
this.
Unfortunately various clients have different db paths and I have set them
up
once on each client location. The problem is that when I send them updates
and they uninstall the old version and reinstall the new version the
setting
is reset to my settings. This is because the old configuration file is
deleted and replaced by the new one included in the app. Is there a way to
have a setting that is not overwritten by an application reinstall?

Whatever install package you're using doesn't it have an exclude file
feature?
Simply, exclude the configuration file in the install setup so that it
doesn't overlay the existing one on the machine during the install.