Links for learning Windows Azure storage

Create an application that stores a file in Windows Azure storage.

How to Create a Storage Account for a Windows Azure Subscription.

How to Register a Custom Subdomain Name for Accessing Blobs in Windows Azure.

Configuring Storage Account Connection Strings.

Browsing Storage Resources with Server Explorer


Enumerating Blob Resources

Delete a Blob

CloudBlob Class

CloudBlobContainer Class

Microsoft.WindowsAzure.StorageClient Namespace

Windows Azure Storage Services REST API Reference


Using Microsoft Windows Azure to Host Web Services and Apple Push Notifications for your iOS Apps.

Windows Azure is looking like an excellent choice for hosting web data and services for mobile apps. Much work is being done by Microsoft to support the hosting of services for the iPhone and iPad (as well as Windows Phone and Android). This even includes support for hosting an Apple Push Notification Service provider. Unfortunately, I have yet to find a definitive guide for this – and it is evolving all the time. Anyways, here’s some links to the best resources I’ve been able to find on the web.

April 14, 2011

Video from Mix11: Developing iPhone and iPad Apps that Leverage Windows Azure – Simon Guest.
Demonstrates uploading an image to Blob storage, inserting a row in Azure table storage and (too briefly) using the Apple Push Notification (APN) service.

Here’s a link to a blog post and the code from the above presentation.

21 Apr 2011

Simon Guest. Using Apple Push Notifications from Windows Azure. This is the only page I have found, so far, where actual code is shown!

May 9th 2011

Blog entry on MSDN about the new release of the IOS Toolkit for Windows Azure.

Video: Deploying the Cloud Ready Packages for Devices

May 11 2011

Wade Wegner Video on “Getting Started with the Windows Azure Toolkit for iOS

Jul 25 2011

Vittorio Bertocci’s Video on “Using the Windows Azure Access Control Service in iOS Applications

Aug 31 2011

Wade Wegner “Windows Azure Toolkit for Devices“. Demo of v1.2.1 of the iOS Toolkit for Azure.

Finally, here are the links to the associated files in GitHub:

Windows Azure Toolkit for iOS (Library)

Cloud Ready Package for Azure

Local vs Global Resource Files in ASP.NET

One question developer’s eventually ask themselves when localizing APS.NET web apps using resource files is why the hell would anyone use local resource files when the advantages and simplicity of using global resource files seems so obvious?

The closest I have got to any definitive guidelines from Microsoft is this passage from the “ASP.NET Web Page Resources Overview” on MSDN

Choosing Between Global and Local Resource Files

You can use any combination of global and local resource files in the Web application. Generally, you add resources to a global resource file when you want to share the resources between pages. Resources in global resource files are also strongly typed for when you want to access the files programmatically.

However, global resource files can become large, if you store all localized resources in them. Global resource files can also be more difficult to manage, if more than one developer is working on different pages but in a single resource file.

Local resource files make it easier to manage resources for a single ASP.NET Web page. But you cannot share resources between pages. Additionally, you might create lots of local resource files, if you have many pages that must be localized into many languages. If sites are large with many folders and languages, local resources can quickly expand the number of assemblies in the application domain.

When you make a change to a default resource file, either local or global, ASP.NET recompiles the resources and restarts the ASP.NET application. This can affect the overall performance of your site. If you add satellite resource files, it does not cause a recompilation of resources, but the ASP.NET application will restart.

The ClientSide API for the ASP.NET Validation Controls

Page_IsValid – A global boolean variable indicating if the page is valid.

Page_Validators – An array containing all the validation controls on the page.

ValidatorValidate(Validator) – Calls the validation function for a specified Validation control. Validator is an actual control reference, not an id.

This will update the global Page_IsValid boolean variable.

Page_ClientValidate() – Calls the validation routine for all validation controls in the Page_Validators array. This will update the global Page_IsValid boolean variable.