Few hours ago I delivered a session about creating Silverlight/XNA hybrid applications for Windows Phone Mango. I like to thank all the participants – you were great and I had a great pleasure to present for such quality audience. I loved the questions and the conversation after the session. The slides deck I used for presentation can be download from the here. As promised, the demo applications also published and can be downloaded from the following locations: Demo #1 is here. Demo #2...
My sessions made into short voting list to TechDays Canaga 2011. My sessions are: WIN314 - Mango: Silverlight and XNA – Better together! WIN319 - Mango: Search Integration WIN320 - Mango: Background Agents at Work Vote for my sessions at: http://bit.ly/tdcan2011vote Thanks, Alex
Windows Phone Mango adds few more task over initial Windows Phone (RTM) release. This post will cover new task (launchers and choosers) added to Windows Phone Mango Beta and Beta 2. To introduce those features I’ve created sample application which looks very simple, yet have all those new tasks: Before we are starting, one very important note about tasks in general. Some of them works on emulator as on real device (Bing maps, Bing directions, etc.), some of them works but doesn’t produce any “visible” output and cannot been verified (Save Ringtone) and some of...
Microsoft just released Beta 2 refresh of Windows Phone Mango developer tools!
The refresh further improves the tools, resolves bugs from previous release and adds some new features.
Most important – registered Windows Phone developers with retail device will get access to Mango updates via invites to Microsoft Connect site which will give them access to Mango for their retail devices!
Also, the release brings some breaking changes which we as developers need to be aware of. Here are the list of some breaking changes:
Image decoding moved to the background thread
Enables more responsive UI
If background loading of an image is not...
This post is a “missing part” of series about new features in Windows Phone Mango
New and very important feature of Windows Phone “Mango” Developer Tools is the profiler. The profiler enables the developers of Silverlight applications (currently only Silverlight scenarios are supported) to sense important heartbeats of the application and collect information about application behavior at runtime.
To measure the performance or the application, navigate to Debug menu option and select Start Windows Phone Performance Analysis:
Visual Studio provides the developer with configuration setting screen which enables him to define some profiling settings, like drawing details, depth of stack frames...
Mango introduces some changes in Push Notifications mechanism which enables the developers to create more attractive scenarios.
First feature I’ll show in this post is a secondary tiles for application. Before Mango, every application could have only one pinned tile on the main screen which could be updated using Push Notification mechanism (I blogged about it quite some time ago here and here).
Mango release enables to have additional tiles which can be pinned and removed from application code! How about having something like this:
All the tiles (beside IE9) on main screen are related to sample I’m going to show...
Windows Phone RTM didn’t allowed to mix Silverlight and XNA content. Mango enables the scenarios where Silverlight content can be rendered along with XNA content. In the sample presented in this post we will build 2-pager Silverlight application with pure Silverlight page (1st page) and mixed 3D XNA & Silverlight page (2nd page).
Final application looks like the following:
In order to ease on the developers, after installing Mango developer tools, Visual Studio provides us with two templates – one in Silverlight for Windows Phone area and one in XNA Game Studio 4.0 area:
The templates are almost identical. The first one...
The Windows Phone RTM operating system had only one active application and when application were sent to the background the state was serialized and kept in the application’s isolated storage. This process called tombstoning and application in such state called tombstoned. When user return to the tombstoned application, he would have to wait a while as the application deserialized its state and recovered and we as developers had to take care about saving the application’s state and resuming it.
With Mango that is no longer the case: there is only one active (foreground) application, but once an application is sent...
One of most requested and discussed features of Mango release is “multitasking”. In Mango the multitasking term has slightly different meaning than standard (PC) multitasking. Multitasking for Mango phones means ability to execute the code while application in not active and play audio started by the application in a background. This is achieved by Background Agents. In addition to them Mango also introduces APIs to download and upload files while application is in the background and add Reminders and Alarm to grab user attention.
This post will show how to use those features. During the post I’ll show how to...
All Windows Phone 7 devices equipped with camera. The minimum required camera resolution is 5 Mega pixels. For developers accession camera information enables many scenarios like image recognition, video chatting, augmented reality and others. From the beginning, Windows Phone 7 RTM devices supported camera usage scenario via launchers and choosers. Phone shell API provided the developer with CameraCaptureTask which could be used to take a picture and use it in the application. This scenario based on phone’s operation system camera interface and not covered in this post. In this post I’ll cover live camera input.
To use live input from...