You can prevent this different ways:
1) custom action that will merge the new app.config with the old uers
app.config if one exists
2) externalize the user settings (seperate config)
Personally i would consider externalizing the settings for printers and
others if these are user specific.
Gabriel Lozano-Morán
"Michael White" <xx*@yyy.comwrote in message
news:O9**************@TK2MSFTNGP04.phx.gbl...
In my app.config file there are various user settings for printers, etc
that
the user may customize. When I publish an update using Click-once and the
app installs the latest version to the user's computer, the config file is
overwritten and the user's modified settings are gone. How do I prevent
this
behavior?
Thanks
Michael