Does the new Azure SDK 1.7 and enhanced publishing allow automating of publishing static files to blob storage?

2
votes

Does anyone know if there have been any changes in Azure publish to allow automatically putting static content (js, css, images) etc to blob storage as part of the publish operation?

This would make it significantly easier to publish applications as you wouldn't have to keep putting static files to blob storage. It makes sense to keep static files off the web role as it will help scale the application.

One of the major benefits Azure has over other development environments should be it's integration with Visual Studio and a good full stack experience

3
azurepublishazure-storage-blobs
I have not heard of any changes in this area re: deployment for blob storage, I could be wrong! - user728584
No neither have I. Just hoped as this release was supposed to be heavily focused on making the deployment process easier. - GraemeMiller
There was soooooo much released on June 7th that this one might have slipped under the radar, live in hope but I don't think so ;) The Web Site www.mygreatwindowsazureidea.com used to be good for asking the Product Team for features, I have never actually seen anyone ask your questions before, interesting! - user728584
Yeah. I'm not bashing MS 7th of June update was huge (hence I wondered if this had been slipped in and I missed it). I just added a comment on the make windows azure deployment easier area. I have mentioned it in a previous question here somewhere. - GraemeMiller

3 Answers

2
votes

The short answer is no - nothing in the v1.7 tools or project type that includes Windows Azure Storage content as one of its elements. I do see the appeal though, in a dev environment. For production systems, I feel that automated tools are more appropriate.

Not that this is the answer you were looking for, but... There's a way you can automate storage upload, though. You can take advantage of PowerShell, combined with your automation tool of choice (whether you're using TFS/MSBuild 100% or mixing in Team City, CruiseControl.net or something else).

The REST API already covers storage management (including the ability to upload block and page blobs). The PowerShell cmdlets make this very easy to upload blob content, and this lets you decide when to execute the script (along with deployment, before deployment, as an update later, etc.).

One more thing to consider: Static content can be enormous in size. You may want to avoid a total upload, and focus on individual objects. Some of the partners I've worked with have hundreds of MB of static content (and several have GBs). Not very practical for pushing this content in one big batch. The PowerShell cmdlets help in these cases.

2
votes

A slightly longer answer is that the CDN kind of makes the decision as between a web role and storage a moot point. At least for the commonly used static files that are used throughout a site.

You can use your hosted service as the Origin server for distribution out through the CDN. Take a look at http://blogs.msdn.com/b/scicoria/archive/2011/07/10/hosted-service-as-a-windows-azure-cdn-origin-tips.aspx

However, as David notes above there may be some benefits in terms of trimming down your release package size by moving these to blob storage during your packaging process. it's be easy enough to script as part of the automated build process and then do differential updates.

1
votes

I've just published https://github.com/Plasma/AzureBlobUtility which is a command line utility to upload a file from local storage to blob storage, which I'm now using to have TeamCity upload cspkg's to blob storage in advance.

You may be find it useful to automate the uploading of your assets.