I’m wrapping up work on the first version of my Azure Framework, hoping to get it documented and posted soon, but in doing my work I’ve made a minor change to the AzureBlobLoader utility, a command line utility that loads files to Azure Blob storage. It now supports the Archive flag, meaning it will only upload files in a directory that have changed, cutting down on processing time and costs.

AzureBlobLoader.exe -? -s[haredkey]:AzureSharedKey -e[ndpoint]:AzureEndPoint
                    -a[ccount]:AzureAccount -c[ontainer]:BlobContainer
                    -f[rom]:StartingDirectory -filter:FileFilter -archive
        -? shows this message
        -s[haredkey] your Azure Shared Key
        -e[ndpoint]  your Azure Endpoint
        -a[ccount]   your Azure Account
        -c[ontainer] the Container where the blobs are to be stored
                 The container will be created if it doesn't exist.
        -f[rom] the starting directory location. If not specified, the
                directory the program is run from will be used
        -filter a file filter to be applied. * matches all, ? matches one letter
                 if not included, will be where the application was run from
        -directory Flag to store blobs with directory structure
        -archive Flag to store blobs with archive attribute set.
                Resets ArhiveAttribute