title: How to persist changes in a .settings/.config file across a file version change?
body: <p>I have created an application that uses settings.settings to store some user specific settings (scope=User).  Settings are loaded correctly on startup, changed during use and saved correctly for next launch.  This cycle appears to have no problems.</p>
  
  <p>The problem arises when I update the assembly and file versions for a new build.  The settings are no longer loaded on startup (instead the default values are used).  It also appears that a config file saved from version 1.1 will persist even if version 1.2 is launched and a NEW config file is generated and saved too (i.e. you can relaunch version 1.1 and the config file will be the config file that was saved from that version).</p>
  
  <p>So it appears that the settings are specific to the version of the assembly and/or file.  It is also worth noting that between version 1.1 and version 1.2 there were no changes to the settings.settings file or anything else for that matter (i.e. the only change I made between these different builds was modifying the version numbers).</p>
  
  <p>Is there a way to persist these settings across version changes?</p>