title: User-scoped settings in ASP.NET
body: <p>I have a class library used in windows (WPF) and web (ASP.NET) context. The library has settings that are rather user-scoped, if used in windows context and that have to be application-scoped, if used in web context. I would like to declare them as user-scoped and use the default values as “pseudo-application-scoped”.  My problem is, that web applications ban user-scoped settings by throwing a configuration error.</p>
  
  <p>What is the best way to handle this, preferably within the frameworks configuration system?</p>