Windows Phone 7 + Azure….and a couple of nuggets…
I recently gave a talk about Windows Phone 7 at a Bizpark Camp in San Francisco. The camp had two focuses: Azure and Windows Phone 7. My presentation covered WP7 portion of the camp. During my presentation I highlighted the phone platform and talked about some of the differentiators from design, technology and a business standpoint.
Whenever I watch presentations or go to tech meet-ups I feel like I get the most value when I can walk away with a few “nuggets” that I wouldn’t necessarily have known about otherwise. That said, I tried to add a few resources into my presentation that should be helpful when building WP7 apps.
Seeing that the camp was focused on Azure and WP7 I decided to augment my presentation with a code sample. The intention was to give some insight on how to approach building WP7 applications that talk to Azure. Some colleges of mine here at Clarity have posted a sample on codeplex focused on getting up and running with WP7 and Azure..you can check it out HERE. The project is not a “hello” world app, and is targeted at people who have some experience with the platform and a working knowledge of silverlight.
Also, during my presentation I mentioned some limitations with the current phone sdk. Our sample code on contains workarounds for the following:
#1 Panorama Control
#2 “Tilt” effect
#3 Animating Frame
#4 Sample architecture (leveraging MVVM light) and coding patterns.
Note: For the sample phone project we used an azure token that will expire in the next couple of months. When that happens…in the downloads section of the codeplex project there a link to a local development fabric that can be used for local development
Admittedly, the slide deck is pretty design heavy, and doesn’t contain much text. This was semi-intentional to encourage people to come out to the camps and hear it first hand. There is some additional info found the “notes” of the PPTX.presentations from eklimcz.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)