Justin,
Isolated storage is a good idea, because you can scope it on the user
level, so you should have no problems there.
I also believe in .NET 2.0 there is a way that you can create user
settings in your config file. Check the System.Configuration namespace for
the classes/attributes that are prefixed with "user". There are a few code
samples that should help you pull it all together.
The advantage of isolated storage over the config settings is that the
files with the users preferences (or whatever you store) will all be in
separate files which should only be accessible to the users that they were
meant for (or an administrator who has rights), whereas with the config
file, I believe all the settings are in one file (I could be wrong here).
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Justin Creasy" <ju***********@gmail.com> wrote in message
news:11*********************@g44g2000cwa.googlegro ups.com...
Hello, I am trying to add the ability to save my applications settings
for each user. I was just wondering what the best method is to do this.
The only requirement is that any user account (user, power user, admin)
will have this capability. I would also prefer to have some measure of
security, but if need be I can use my own methods to handle this.
I am currently writting the setting information to the "application
data/all users" folder and I'm getting complaints from beta testers
that this is not working for user and power user accounts. Should I
continue to use application data and maybe do something different, or
should I use the registry or maybe Isolated Storage?