Why the dumb rule about app scoped settings being read-only??

  • Thread starter Richard Coltrane
  • Start date
R

Richard Coltrane

Hi,

Im wondering why there is a rule that says application scoped settings
should be readonly?? Surely application scoped settings are just that;
scoped at the application level... the same settings for all users. Period.
Why have Microsoft arbitrarily decided they should be readonly as well? It
strikes me as a rediculously unneccessary restriction that leaves me having
to "roll my own" anyway.

They seem to have confused scope with function?

Anyone else think this is just plain dumb?

Richard
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Persisting Application Scoped Settings 2
Why force a connection string scope to be application? 8
How to suppress repeating password prompts and scope pre-emption? 3
user settings for a dll; and a 2nd ? about Friend Assemblies 2
CryptoLocker virus 3
Global subroutines 1
.NET GC Woes & Best Practices 15
Setting up a multiple user environment & XP administration in gene 4

Top