Are the settings application scoped or user scoped? If they are application
scoped, they are read-only (the reason for this is because the settings are
backed by the application.exe.config file which is read-only for normal users
whereas user scoped settings are backed by a file that is located under the
current user's documents folder)
- Stenis
[quoted text, click to view] "martin.lundberg@gmail.com" wrote:
> Hello!
>
> (If this is the wrong place to ask this, maybe there's a Whidbey or VS
> 2005 newsgroup somewhere, please direct me to the right place)
>
> I've been trying to figure out how to work with the VS 2005
> client/application settings but I can't make it work.
>
> I can go to the project properties and choose the settings tab where I
> can enter different settings. But I can't change it att runtime.
>
> If someone could be nice enough to give me an code example of how I
> could enter a setting, change it at runtime and save it, I would be
> very grateful!
>
> Thanks in advanced!
>
Hello! =)
I found this out myself just today. I had them application scoped. I've
tested with user scoped and it works. I'm just wondering, in the
documentation the say that most application settings (those application
scoped) are read-only, most. Is there a way then to write to them and
save?
Thanks for the answer anyway! =)
It is possible to write your own settings provider to provide this
functionality, but there is no built-in support for persisting application
scoped settings in your application.
- Stenis
[quoted text, click to view] "Lundberg" wrote:
> Hello! =)
>
> I found this out myself just today. I had them application scoped. I've
> tested with user scoped and it works. I'm just wondering, in the
> documentation the say that most application settings (those application
> scoped) are read-only, most. Is there a way then to write to them and
> save?
>
> Thanks for the answer anyway! =)
>
Don't see what you're looking for? Try a search.
