Webcast windows phone 7

Privacy Statement. See System Requirements. Available on Mobile device. People also like. Skype Free. Netflix Free. Windows Insider Free. Upgrade WP Free. Microsoft Authenticator Free. Additional information Published by Inventos. Published by Inventos. Developed by Inventos. Approximate size KB. Age rating Not Rated. Category Music. Installation Get this app while signed in to your Microsoft account and install on up to ten Windows 10 devices. The contest ends on December 31, — so get slinging that code now peoples!

As a developer, one of the things I love about my Windows Phone 7 is that it is really easy to write applications for it. I already have Visual Studio , already know. NET, and know just enough Silverlight to be dangerous. Since I work with Windows Azure all the time now, being able to easily combine my Windows Phone 7 apps with the power, flexibility, and ease of Windows Azure just warms the cockles of my geeky heart!

Why, you say? Well, besides being one of the cool kids and earning the admiration of all your friends, you can also win a slick Samsung Series 7 Slate! But wait. So what are you waiting for! There have been quite a few recent updates to the Windows Azure Platform. This post is partially to serve as a reminder to me of some of the new areas of the platform I need to dive into, and partially to help spread the word about many of the new innovations available today.

This is the first of probably several posts this week. BUILD is going on now. When logging into the new SQL Azure Management Portal, you may be presented with an error related to your firewall rules.

Verify the error was related to the SQL Azure firewall rules, update your rules, and try to log in again. The new Tables page provides an easy to view listing of all the tables in the selected tables.

The icons for those actions are easy to recognize — very Metro UI like. Windows Azure Autoscaling Application Block. My answer so far has always been along the lines of automatically scaling an application is often not a trivial operation, and that there are lots of things to consider when scaling elasticity — both in and out, cost implications, what metrics to use for scaling, etc.

If you wanted some autoscaling features, you were often left with either writing a solution yourself or working with a provider such as Paraleap and their AzureWatch service. That story looks like it is about to change. Look here for a future post soon demonstrating some of the features of the Windows Azure Autoscaling Application Block. Another common ask when speaking with people about Windows Azure and SQL Azure is related to how to synchronize their data.

The newly released Microsoft Sync Framework v4 looks to help solve this problem. Recently I was working on putting together a sample of how to use the service relay feature of the Windows Azure Service Bus. By using the Windows Azure Service Bus as a service relay, it is possible to expose on-premises services in a secure way, without the need to punch holes in your firewall or stand up a lot of new infrastructure. Part of the sample included accessing the service from Windows Phone 7.

Easy enough, right? Setting up the server side to register on the Service Bus is fairly straightforward. However, I do want to be sure to point out that services can have one of two types of client authentication — none and an access token.

Adding a security token ups the complexity a little. By requiring an access token a client would need to authenticate with Windows Azure Access Control Services first, and then provide the token as part of the service call. An area that can be confusing when dealing with authentication in this situation is the Service Bus still uses ACS v1 for authentication, not the newer, cooler, ACS v2.

Now that I had the server side set up, it was time to work on the WP7 side of the sample. As I mentioned before, there are a lot of samples available for setting up both the service and client side of a Service Bus connection. WebClient behaves a little differently on WP7 than it does on a desktop or server app. For my sample I decided to go with what is the most basic form of authentication, a shared secret.

There are a few things to point out about this code. So, now we need the code to handle the response. That code will need to extract the ACS token from the response and pass it on to the service.

The key, at least for me, was the line which decodes the token received from ACS. Note — ParseAndShowResult is simply a helper method to parse the result of the service call and show on the phone, so nothing exciting going on there.

The problems for me were really related to a lack of understanding of what was needed with regards to authenticating with ACS and likely a little inexperience in working with REST services. Hopefully this quick sample will save someone else from some frustrating AM coding sessions. The firestarter is an all day event designed to give developers a jumpstart on creating exciting Windows Phone 7 applications that leverage the power and flexibility of the Windows Azure platform.

The day will feature 4 sessions — 2 on Windows Phone 7 and 2 on Windows Azure. There will also have dedicated time set aside for you to work on labs to help you hone your skills and gain some valuable hands-on experience. After all, the best way to learn about a technology is to use it, right? The firestarter will be held from am — pm at the Microsoft office in Columbus.

This is the third update in less than 2 months! It is great to see the teams moving so quickly to get new updates out.

The second update v1. This third update v1. Wade Wegner recently teased a few of these updates. Enter the namespace and key into the wizard when prompted. The toolkit will handle the rest for you.