This question describes my problem exactly, except I'm using a custom configuration section in app.config
with ConfigurationManager
, so the solution presented there doesn't apply...
Basically, my problem is that when ClickOnce updates the application, it installs into a different directory with the new app.config, thereby erasing any changes made. My application uses app.config to persist application settings, so this is very bad... a merged update would be excellent (similar to what is achieved in the other question), but just about anything automated would be good at this point.
Or should I just use a set location for my app.config file rather than try to use the default location?