Settings scope dilemma

Settings scope dilemma

Old forum URL:

Q Johnson posted on Thursday, April 07, 2011

I would like to have my user AppSettings available to ALL users. 

If I make them Application settings, they can all see and use the values, but they can't change them.  And if I make them User settings, which they CAN change, then they are only visible to the specific user and I want them to have All User scope.

Users who install our product on a workstation don't mind filling out the settings once and going forward with their own unique setup.  But I've got a client running this on a citrix server and they think it's a big deal to have to re-enter the values for each user that is going to acces the program.  And I kind of agree with them.  Isn't there some EASY way to have the users get and set this settings data?  Or must I resort to writing and parsing a custom text file saved in the AllUsers Application Data folder or, worse still, adding yet another table to the database to hold these values that everyone will be using?

Thanks in advance.



RockfordLhotka replied on Thursday, April 07, 2011

The System.Configuration namespace (once you reference that assembly) has all sorts of flexibility. I haven't looked deeply at that stuff for many years, but I'm pretty sure you can have multiple config files, in different places, or even in a database, and still have everything available through the standard config API.

JCardina replied on Friday, April 08, 2011

We store every possible setting we can in the database itself and use business objects to back them.  There is only one setting we don't store in the db and that's the connection string.

Copyright (c) Marimer LLC