title: Trying to save strings in Azure blob storage with C#, getting strange errors
body: <p>I'm making an API call to a website, getting back some data and trying to save it as a blob in Azure blob storage. </p>
  
  <p>I'm getting strange exceptions in my debug output window, but they're not coming up on in my try/catch exception handling (I've got a breakpoint set there as well.) The data is not saving in Azure.</p>
  
  <p>Here is my code:     </p>
  
  <pre><code>CloudStorageAccount storageAccount = CloudStorageAccount.Parse(
              CloudConfigurationManager.GetSetting("connectionString"));
  CloudBlobClient blobClient = storageAccount.CreateCloudBlobClient();
  CloudBlobContainer container = blobClient.GetContainerReference("data");
                  container.CreateIfNotExists();
  CloudBlockBlob blockBlob = container.GetBlockBlobReference($"{measurementString}.json");
  await blockBlob.UploadTextAsync(resultContent);
  </code></pre>
  
  <p>With a breakpoint, I can see the container is created.</p>
  
  <p>And I get this exception:</p>
  
  <pre><code>Exception thrown: 'System.Net.WebException' in System.dll
  Exception thrown: 'System.Net.WebException' in System.dll
  Exception thrown: 'Microsoft.WindowsAzure.Storage.StorageException' in Microsoft.WindowsAzure.Storage.dll
  Exception thrown: 'Microsoft.WindowsAzure.Storage.StorageException' in Microsoft.WindowsAzure.Storage.dll`
  </code></pre>
  
  <p>My .NET version is 4.5.2, and my package versions are:</p>
  
  <pre><code>Environment: &lt;packages&gt; &lt;package id="Microsoft.Azure.KeyVault.Core" version="2.0.4" targetFramework="net452" /&gt; &lt;package id="Microsoft.WindowsAzure.ConfigurationManager" version="3.2.3" targetFramework="net452" /&gt; &lt;package id="WindowsAzure.Storage" version="8.1.3" targetFramework="net452" /&gt; &lt;/packages&gt; 
  </code></pre>
  
  <p>When I put a breakpoint on await blockBlob.UploadTextAsync(resultContent);, it never comes up! </p>
  
  <p>EDIT: I changed the blob name string .ToLower() and it seemse to be working fine now. I guess that was it!</p>