User Settings

[Steve Barnett]

I added some user settings to my app which caused the Settings.settin gs to
be generated etc... and all was well and lovely and the Sun was shining.

Then I changed the version number of my assembly (it had been updated, after
all) and all of my settings disappeared, which was somewhat less than lovely
and the clouds came rolling in.

I gather the user.config file that the Properties.Sett ings class saves is
assembly version specific. Is there any way to override that so I can retain
the settings across all versions of my app?

Thanks
Steve

[Steve Barnett]

Is it that no one uses the generated Settings class and user.config file?

Perhaps I'm wasting my time with this feature?

Anyone have an opinion?

Steve

"Steve Barnett" <no****@nodomai n.comwrote in message
news:ec******** ******@TK2MSFTN GP03.phx.gbl...

>I added some user settings to my app which caused the Settings.settin gs to
be generated etc... and all was well and lovely and the Sun was shining.

Then I changed the version number of my assembly (it had been updated,
after all) and all of my settings disappeared, which was somewhat less
than lovely and the clouds came rolling in.

I gather the user.config file that the Properties.Sett ings class saves is
assembly version specific. Is there any way to override that so I can
retain the settings across all versions of my app?

Thanks
Steve

[Peter Duniho]

On Tue, 18 Dec 2007 05:14:50 -0800, Steve Barnett <no****@nodomai n.com>
wrote:

Is it that no one uses the generated Settings class and user.config file?

Perhaps I'm wasting my time with this feature?

Anyone have an opinion?

I use it all the time. But I don't have the requirement to preserve the
settings across updates of my programs, so I've never actually had to
solve the problem you're asking about.

I can't speak for everyone else, but just because you haven't received a
response to your question, that doesn't mean no one's using the feature.
At best, it means no one's trying to use it the way you want to use it.

That said, I suspect there _is_ a solution to your problem. I think the
Settings class would be much less useful if users had to start from
scratch every time the program was updated. I just don't happen to know
what that solution is. Sorry...

Pete

[Kevin Spencer]

Hi Steve,

I use User Setting quite often, but have never tried to deal with the issue
of persisting settings across versions of the application. I suspect that
the best way to do this would be to use the System Registry for such
settings, as it is in a well-known location that will not change, and will
persist the settings as long as either your application or the user removes
them.

--
HTH,

Kevin Spencer
Chicken Salad Surgeon
Microsoft MVP

"Steve Barnett" <no****@nodomai n.comwrote in message
news:ep******** ******@TK2MSFTN GP02.phx.gbl...

Is it that no one uses the generated Settings class and user.config file?

Perhaps I'm wasting my time with this feature?

Anyone have an opinion?

Steve

"Steve Barnett" <no****@nodomai n.comwrote in message
news:ec******** ******@TK2MSFTN GP03.phx.gbl...

>>I added some user settings to my app which caused the Settings.settin gs to
be generated etc... and all was well and lovely and the Sun was shining.

Then I changed the version number of my assembly (it had been updated,
after all) and all of my settings disappeared, which was somewhat less
than lovely and the clouds came rolling in.

I gather the user.config file that the Properties.Sett ings class saves is
assembly version specific. Is there any way to override that so I can
retain the settings across all versions of my app?

Thanks
Steve

[Steve Barnett]

My concern over using the registry or well know locations was with Vista
security. I was unsure as to what it may or may not limit me to. Similarly,
what about security policies that system administrators put in place. The
user settings seemed to be a safe (Microsoft) way round this.

What I've done for now is throw together my own class to wrap "ini" file
functionality using an xml file. It allows me to control where the file goes
and what it's called and I don't need to worry about application version
numbers. I've used a "well known location" and am just hoping it won't get
locked down by Vista. (It's the users Application Data folder - since, on
reflection, I'm saving application data - folder locations - rather than
pure user data.).

I sacrifice strong typing using this method, but you can't have everything.

Thanks
Steve

"Kevin Spencer" <un**********@n othinks.comwrot e in message
news:uR******** ******@TK2MSFTN GP02.phx.gbl...

Hi Steve,

I use User Setting quite often, but have never tried to deal with the
issue of persisting settings across versions of the application. I suspect
that the best way to do this would be to use the System Registry for such
settings, as it is in a well-known location that will not change, and will
persist the settings as long as either your application or the user
removes them.

--
HTH,

Kevin Spencer
Chicken Salad Surgeon
Microsoft MVP

"Steve Barnett" <no****@nodomai n.comwrote in message
news:ep******** ******@TK2MSFTN GP02.phx.gbl...

>Is it that no one uses the generated Settings class and user.config file?

Perhaps I'm wasting my time with this feature?

Anyone have an opinion?

Steve

"Steve Barnett" <no****@nodomai n.comwrote in message
news:ec******* *******@TK2MSFT NGP03.phx.gbl.. .

>>>I added some user settings to my app which caused the Settings.settin gs
to be generated etc... and all was well and lovely and the Sun was
shining.

Then I changed the version number of my assembly (it had been updated,
after all) and all of my settings disappeared, which was somewhat less
than lovely and the clouds came rolling in.

I gather the user.config file that the Properties.Sett ings class saves
is assembly version specific. Is there any way to override that so I can
retain the settings across all versions of my app?

Thanks
Steve

[Kevin Spencer]

Hi Steve,

Considering your decision regarding approach, you could still use User
Settings. All you would have to do is to copy the existing User Settings to
your installation Settings file. It is, after all, just an XML file
containing a serialized class.

--
HTH,

Kevin Spencer
Chicken Salad Surgeon
Microsoft MVP

"Steve Barnett" <no****@nodomai n.comwrote in message
news:Oo******** *****@TK2MSFTNG P06.phx.gbl...

My concern over using the registry or well know locations was with Vista
security. I was unsure as to what it may or may not limit me to.
Similarly, what about security policies that system administrators put in
place. The user settings seemed to be a safe (Microsoft) way round this.

What I've done for now is throw together my own class to wrap "ini" file
functionality using an xml file. It allows me to control where the file
goes and what it's called and I don't need to worry about application
version numbers. I've used a "well known location" and am just hoping it
won't get locked down by Vista. (It's the users Application Data folder -
since, on reflection, I'm saving application data - folder locations -
rather than pure user data.).

I sacrifice strong typing using this method, but you can't have
everything.

Thanks
Steve

"Kevin Spencer" <un**********@n othinks.comwrot e in message
news:uR******** ******@TK2MSFTN GP02.phx.gbl...

>Hi Steve,

I use User Setting quite often, but have never tried to deal with the
issue of persisting settings across versions of the application. I
suspect that the best way to do this would be to use the System Registry
for such settings, as it is in a well-known location that will not
change, and will persist the settings as long as either your application
or the user removes them.

--
HTH,

Kevin Spencer
Chicken Salad Surgeon
Microsoft MVP

"Steve Barnett" <no****@nodomai n.comwrote in message
news:ep******* *******@TK2MSFT NGP02.phx.gbl.. .

>>Is it that no one uses the generated Settings class and user.config
file?

Perhaps I'm wasting my time with this feature?

Anyone have an opinion?

Steve

"Steve Barnett" <no****@nodomai n.comwrote in message
news:ec****** ********@TK2MSF TNGP03.phx.gbl. ..
I added some user settings to my app which caused the Settings.settin gs
to be generated etc... and all was well and lovely and the Sun was
shining.

Then I changed the version number of my assembly (it had been updated,
after all) and all of my settings disappeared, which was somewhat less
than lovely and the clouds came rolling in.

I gather the user.config file that the Properties.Sett ings class saves
is assembly version specific. Is there any way to override that so I
can retain the settings across all versions of my app?

Thanks
Steve