title: Best way to store settings (special requirements)
body: <p>I found a lot of information for saving different kinds of application/user settings in different places but getting confused what could be the best way for me.</p>
  
  <p>My problem has different dimensions:</p>
  
  <ol>
  <li>The application will have some User-Roles (Admin, StandardUser, ...), where every User (based on Windows-Logon) will belong to one role.
  The Admin is allowed to setup everything for everyone.</li>
  <li>The settings have different categories:
  <ul>
  <li>Application settings (should be the same for every user on the computer)</li>
  <li>User-Role-specific settings</li>
  <li>User-specific settings</li>
  </ul></li>
  <li>The application has several projects where different projects have to access the settings.</li>
  </ol>
  
  <p>(4. The application is written in C#)</p>
  
  <p>I don't want to mention the things that I have read because I don't want to steer your thoughts into a (maybe wrong) direction.
  So, how would you handle this scenario?</p>
  
  <p>Thanks a lot!!
  Joerg</p>
  
  <hr>
  
  <p><strong>EDIT 1</strong></p>
  
  <p>Some more things after the first answers that I hope can clarify my question:</p>
  
  <ul>
  <li>my question doesn't focus on the authentication of the users, it focusses on create/edit/save settings</li>
  <li>my first attempts for solving the problem were:<br>
  <ol>
  <li>using the Visual Studio Settings.Settings file<br>
  ... doesn't work because I have several projects that have to have access to the settings AND I couldn't find a way to make the ApplicationSettings writeable (they are readonly)</li>
  <li>use the <code>ConfigurationManager</code>-Class<br>
  ... I am not experienced with this one but as far as I understand this class it is just another class that gives me access to my ApplicationSettings (and has the same problems like #1)<br>
  ... maybe a link to a <em>good</em> tutorial will help</li>
  <li>invent something on my own<br>
  ... I still hope to find something ready-to-use</li>
  </ol></li>
  </ul>