assemblyversions

I'm looking for pointers, suggestions, and even dictation on how to manage the three different assembly version numbers for a .NET assembly. The Product version is the simplest, as this seems would normally be dictated by business. Then, the file version seems to be for versioning between deployments, where the actual assembly version is only used when shipping. Right now I'm just looking for a simple means of labeling test and maintenance releases of an assembly on which none depend, so I am looking at auto-incrementing build and revision numbers on the file version, and for final release,

Basically the problem is that each time the assembly version changes (i.e. the user installs a new version of the application) all their settings are reset the the defaults (or more accurately a new user.config file is created in a folder with a different version number as the name) How can I keep the same settings when upgrading versions, since using ini files or the registry seem to be discouraged? When we used Clickonce it seemed to be able to handle this, so it seems like it should be able to be done, but I'm not sure how. ApplicationSettingsBase has a method called Upgrade which migrates