I would like to thank the attendees of my “Putting the Cloud in Your Pocket – A Guide to Using Windows Azure to Build Cloud-Enabled Windows Phone Apps” talk at the recent Codestock event – especially considering the early hour following the previous night’s fun. The slide and code content I referred to in my talk can be found here. Also, many thanks go out to the event organizers – I had a great time traveling down to Tennessee for this event, and hope to maybe do so again in the future.
As can be expected, I removed my custom/personal ACS information from the sample code. This includes the acsnamespace and realm resources in the AccessControlResources.xaml file within the Phone project, and the SwtSigningKey, realm, and namespace values from the MVC project’s web.config file. These values can be obtained from a new or existing ACS namespace as follows:
These values are available in the following locations (Note – this is based on the current Silverlight-based management portal. Precise locations may shift slightly when this content moves to the newer HTML5-based portal.)
The namespace value is the namespace you indicated when creating the ACS instance.
The Realm is specific to the relying party application that has been configured, and can be found on the Relying Party Application page:
The symmetric key can be obtained from the Access Control Service management portal, selecting Certificates and Keys, selecting (and/or creating) a Symmetric Key specific to the namespace:
Also, please remember that the code made use of the Async CTP assembly. This was not strictly required, but was instead put in place to help improve the code flow instead of using Lambdas or complete methods for the various callback functions used when interacting with Azure Storage. Information about the Async CTP is available here.