title: CloudConfigurationManager vs WebConfigurationManager?
body: <p>In an Azure Websites I was always using the following code to fetch some values from the config's app settings:  </p>
  
  <pre><code>string property = WebConfigurationManager.AppSettings["property"];  
  </code></pre>
  
  <p>Just a couple of days ago I stublemd upon CloudConfigurationManager, and with it I can get the property like so:  </p>
  
  <pre><code>string property = CloudConfigurationManager.GetSetting("property"); 
  </code></pre>
  
  <p>Although CloudConfigurationManager seems like it's better fitted to cloud use, I never had any issues with WebConfigurationManager.  </p>
  
  <ul>
  <li>Should I be using CloudConfigurationManager?</li>
  <li>What are the differences between the two?</li>
  <li>In what cases CloudConfigurationManager will behave diffrent from<br>
  WebConfigurationManager?</li>
  </ul>