views:

107

answers:

3

What is the preferred way to store user-level information for .NET application. I could have used registry or config files - but some users don't have enough permissions to save/load from these.

I have heard something about assembly private storage or smth like that, is it a way to go?

My main concern is to make sure that even users with a minimal set of priviliges could be able to access this storage location.

+1  A: 

You can use my.settings . Check this page from msdn.

Shoban
That is (unfortunately) vb specific.
Joel Coehoorn
+5  A: 

How about User-scoped Application Settings? (They're stored locally in each user's Local Settings folder.) You can create the settings file using the VS designer as well, and they're pretty easy to maintain.

There's more information from MSDN here about the Application Settings architecture in general, with quite a few more links on that page.

lc
what about required user permission. let's say if I run my app under most restricted account (user-account) - is it (User-scoped Applicaiton Settings) going to work in my case? Thank you LC.
AlexKelos
Unless something's really strange, all users have full access to their own Local Settings folder, so there will be no problems.
lc
A: 

Most applications nowadays use some sort of database to store information. SQL Express and SQLLite can server this purpose.

J.W.