Skip to main content

Windows Phone Training kit updated

Microsoft recently updated the Windows Phone Training Kit. This update includes a refresh to almost all the labs and also includes some new ones.

The 2 added labs are:

  • Accessing Windows Phone 7 Devices is a lab that lets you work with the phone’s camera and location services. The Windows Phone 7 is equipped with a Camera and GPS (global positioning system). Developers can leverage these devices to build location-aware applications and take live photos. The lab walks you through the steps required to integrate your applications with the phone’s camera. The goal is to build an application that lets you capture pictures, give them a title, and save them to the application local store. The lab also gives you the option to “fake” locations and, when saving a picture to a local store, associate its latitude-longitude (lat-long) geo-coordinates, and create a view in which you can see the pictures on a map.  (This lab uses the Windows Phone GPS Emulator).
  • Multi-touch Game Development with XNA Framework is a lab that introduces you to multi-touch enabled game development on Windows Phone 7 using XNA Game Studio, the Windows Phone Developer tools and Visual Studio 2010. During the lab, you will build a simple 2D game using XNA Game Studio. Playing the game requires the user to supply multi-touch input; this lab will show you how to support these inputs while making sure that the game reacts to them as the user would expect.

Some other interesting lab updates are the Using Chooser and Launcher lab that now show the entire Chooser and Launchers family (except the marketplace) and the Using Push Notification lab that now  uses the latest Windows Phone Push Notification Library.

You can download the full kit, or just the Silverlight or XNA framework labs. The online training kit was also updated.

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...