User settings revert to defaults on re-publishing application

[Gino]

If I provide a user with the ability to change some settings in a VS2005
solution using my.settings and then republish the application to fix a bug
or add a new feature the settings get lost due to the change in version
numbers and revert back to my default project settings. I believe the user
settings are saved in a folder which has the application version in its path.

Is there a simple way to get around this or do I need to store all user
settings in a database?


Thanks

 

[Steve Gerrard]

If I provide a user with the ability to change some settings in a
VS2005 solution using my.settings and then republish the application
to fix a bug or add a new feature the settings get lost due to the
change in version numbers and revert back to my default project
settings. I believe the user settings are saved in a folder which has
the application version in its path.

Is there a simple way to get around this or do I need to store all
user settings in a database?


Thanks

1. Are you making the settings User, or Application?

2. Are you changing the asssembly version number, or just the publication
version number?

 

[Steve Gerrard]

Steve,

The settings I am having issue with are marked as application
settings.

On the other front I am changing the assembly version to agree with
the publish release on each publish to identify release deployed from
application.

Is this source of problem?

Thanks for reply

My impression is that only User settings are preserved when a new version is
published. Application settings are ones that the programmer can change, but not
the end user.

I used to think that the assembly version would matter, but now my impression is
that it does not. The assembly name, or application name, plus signature if any,
seems to be the main identification.