Here it is – the Windows Azure Toolkit for Windows Phone 7 v1.2!
As I mentioned last week when I spoke about Updates Coming Soon to the Windows Azure Toolkit for Windows Phone 7, we have some really important and valuable additions to the toolkit.
Support and tooling for the Access Control Service 2.0
Support for Windows Azure Storage Queues
Updated UI/UX for the management web application
These are significant updates – particularly the support for ACS. Given the number of updates since version 1.0 – don’t forget that we added Microsoft Push Notification support, and more, in version 1.1 – I decided to redo the Getting Started with the Windows Azure Toolkit for Windows Phone 7 video.
I highly recommend you take a look at the following resources to learn more:
by Wade Wegner
Vittorio Bertocci: Windows Azure Toolkit for Windows Phone 7 1.2 will Integrate with ACS
We also have a fantastic set of articles on CodePlex that you should take a look at:
Version 1.2 Updates
In version 1.1 we introduced support for Microsoft Push Notification Services. In version 1.2 we default to adding this service, but we give you the option of excluding if it’s not required. Additionally, we also let you choose whether you want to support Apple Push Notification Services in now:
Then, you can easily use the Windows Azure Toolkit for iOS to work with this service running in Windows Azure.
As mentioned extensively by Vittorio, you can also choose to use ACS instead of the simple ASP.NET membership service.
Take a look at this article if you’re trying to determine which type of user authentication you should use. If you go with ACS, this produces a very nice login experience where you can choose one of your existing identity providers.
As with Blobs and Tables, we now provide full support for Windows Azure Queues. This allows you to enqueue and dequeue messages from your application.
Finally, we were not particularly pleased with the out-of-the-box ASP.NET theme, so we updated it. Inspired by the Metro Design guidelines for Windows Phone 7, we came up with something nice and fresh.
We’ve come far along enough now that it’s more important for us to track changes, in particular when they are breaking changes. If you used version 1.0 or 1.1 of this toolkit, I highly recommend you take a look at the Change Log. If you’ve started to use the toolkit for building applications, there are potentially a couple changes you should review. The two I’ll call out here are:
In the AuthenticationService we changed the LoginModel class to Login. This means that you may have to update how authenticate to the membership service.
We changed the CreateUserModel to RegistrationUser, and changed the name of its UserName property to Name. This class is used by the AuthenticationService to register new users.
An affect of these changes could be an error when interacting with user data stored in table storage. For local development, the best thing to do would be to reset local storage so that you don’t have the old schema stored in a table.
We’ll have at least a couple more releases of this toolkit over the next month or two, and I’ll share the details with you as soon as they are locked. For now, please be sure to let us know if you think we should target other scenarios. Submit your feedback on CodePlex and join the discussion!
I hope this helps!comments powered by Disqus