views:

159

answers:

1

Right now when I release a new build of my .NET app, the UserAppDataPath path points to a new folder that includes the build number.

Documents and Settings\UserName\Application Data\Company\AssemblyName\1.0.0.0

I use this path as a convenient storage place for extended user UI setting files. Every time I release the user looses their previous UI settings.

Is it safe to trim off the \1.0.0.0 version number and use its root path? or is there a better way to store settings in a place that is always has write privileges?

A: 

AppSettings do support upgrades. Have a look here. Hopefully this points you in the right direction...

Nader Shirazie
Will that work for files other than the app.config? I have been storing other files along with the app.config?
Tim Santeford
Depends on what you mean by 'other' files, and how they're implemented. Are they custom settings, or using .NET's built in settings support classes? This should work for settings that implement the 'IApplicationSettingsProvider' interface.
Nader Shirazie