Click-once deployments are suppose to maintain user settings, but on this one application we have the user settings are overwritten to the Visual Studio default every time we publish an update. Any ideas of what might be happening?
+1
A:
I have seen this happen when you make a change to the structure of the settings/config file.
If you publish an update w/out changing the structure of the file the settings on end user's machines should be preserved.
Nate Bross
2010-02-04 22:40:29
A:
Regarding ClickOnce and ApplicationSettings. I guess you are in the case:
Setting's default changed; local setting still set to original default in user.config -> The setting is merged into the current version's user.config with the new default as the value
Ando
2010-02-05 07:14:43