Bing Rewards app now available for Windows Phone!

Earning and redeeming Bing Rewards credits just got even easier with the new dedicated Bing Rewards app for Windows Phone – now available for download from the Windows Phone Store. Bing Rewards makes it fun to discover ways that Bing can help you do the things important to you. All you need to do is sign-in and search with Bing. As you search with Bing, you earn credits that can be redeemed for apps and games from the Windows Store or Windows Phone Store. You can also redeem for popular gift cards from top brands, Starbucks, Xbox, Fandango and more or donate your credits to a local school or charity of your choice.

Almost_final2 Almost_final3 Almost_final5

With the Bing Rewards app for Windows Phone, you can now search and earn credits on the go. With the app, you get access to your Bing Rewards dashboard with you can see all your offers, manage your account, redeem credits, enter sweepstakes, and more. You will also get exclusive mobile-only offers for opportunities to earn credits on your Windows Phone.


Pin the app to your Start screen on your Windows Phone and have its Live Tile monitor your credits and the status of your search and earn offers.

See this blog post on the Bing Blog for more details.

Download the app and get started today. If you’ve signed in and done a lot of searches on Bing, you may already have a bunch of credits! I’ve got 1,023 credits I’ve got to decide what to do with… 3-months of no ads on looks enticing.



DVLUP goes worldwide!

Microsoft has announced that DVLUP, the Windows Phone app developer program that Nokia first launched in November 2012, is now available in 192 countries, which means that it its now accessible in nearly every part of the world.

The DVLUP program is basically a way for Windows Phone app creators to engage with each other while also making software for Microsoft’s mobile OS. The program includes a kind of meta-game where developers can earn things like badges and prizes when they unlock achievements on the DVLUP site. There’s also a leaderboard where those same developers can compare their badges, the number of points they have collected, and how many apps they have created for Windows Phone, along with apps made for Nokia X and Nokia Asha devices.

While DVLUP was previously limited to developers who live in the U.S., Canada and parts of Europe, today’s announcement means there should be a ton of new sign ups for the program, Microsoft said, “We are extremely excited to help app developers all over the world in their journey to being successful. If you’ve got apps, we want to help you shine! DVLUP is free to join.”

Nokia releases Imaging SDK 1.2 and pulls Lumia SensorCore SDK out of private beta

Microsoft has updated two of their Nokia Software Development Kits, the Nokia Imaging SDK, as well as the Lumia SensorCore SDK. The Imaging SDK has been updated to version 1.2, while the SensorCore SDK has come out of private beta, and into developer beta.

The Nokia Imaging SDK gives developers a set of image editing and manipulation tools. The tools are designed for performance and devices with smaller amounts of memory. This latest version of the SDK features an Animated GIF Renderer, Image Aligner APT, and Local Blending API. It shares a single code base with Windows 8.1 to make porting to Windows Phone 8.1.

Meanwhile, the Lumia SensorCore SDK has moved to public beta. SensorCore allows developers to use data from a low-powered, motion- and location-tracking processor found in some of the most recent Lumia devices, such as the Lumia 930. This data can be used in application to give users more data about their activity and fitness. Because the data is centralized on this low-power processor, apps don’t need to collect it themselves, updating with new data when they are opened. This decreases battery drain. Users will need to grant permission for apps to collect this data from the device. As reported last month, Bing Health & Fitness already uses the Lumia SensorCore SDK. Below is the video with examples of SensorCore-enabled apps that developers can build.

Marmalade SDK 7.3 for Windows platform: new features, free license

Marmalade, a Windows platform middleware partner, just released a new version of their popular SDK.  The Marmalade SDK enables developers to deploy code across multiple platforms and devices from a single code base. The new 7.3 SDK release brings new capabilities for Windows 8 and 8.1 and Windows Phone 8 across all license types, including Community licenses.  And for new users, the SDK will be available for no license fee. Existing users with Indie, Plus or Pro licenses will get a free upgrade.

The addition of the Extension Development Kit for Windows Store (both Windows 8 and Windows 8.1 apps), enables developers to access Windows managed and native APIs, plus integration with advertising and social networks.

The prior Marmalade SDK 7.2.1 release provided support for features such as Accelerometer, Audio, Compression, Video, and more. Just a few enhancements in this release include APIs to access:

  • Device camera UI and ability to capture frame data
  • Device’s magnetic compass reading
  • Facebook website via Facebook Connect
  • Get the full list here

In addition, this release includes an ads-in-apps extension that support monetization through the Microsoft Advertising SDK or AdDuplex SDK.

Read more about this release, download the SDK and get started today.

325 Windows Phone apps you can launch from your own app!

If you know what an app uri scheme is, you’ll find this resource useful, for sure, as it contains more than 300 uri schemes you can integrate into your app to launch other apps! 🙂

Happy uring 🙂

Installing Remote Tools and Debugging on your Surface

The Microsoft Surface is a new kind of tablet that comes in somewhere between an entertainment device and a work productivity tool. While it looks very similar to the full version of Windows 8 it actually runs Windows 8 RT on the ARM architecture. This means that the previous stable of debugging tools won’t work since they have been designed on the x64 or x86 frameworks. Microsoft has of course taken this into account and has released a new set of remote tools to aid in debugging.

The Surface is not the only WinRT device on the market but currently is the leader and will be used for demonstration and examples in this article.


Step 1

Let’s start by running the remote debugger. Open the apps page and start the ‘Remote Debugger’ application. You can get to the apps page by going to the start screen and hitting Windows Key + Z. Once it starts open the options menu item under file if it did not come up initially.

Debugger Options

On this page you will find the following authentication options.

  • Windows Authentication – Use if you are on an untrusted network or you use the same account information to access both devices.
  •  No Authentication – Use this if you are on a private network or you do not have the same accounts on both the computer and tablet.

Tip: Try to run both devices on the same network so that there is a reduced chance of a network firewall stopping the connection.

If the application is ready you will see a message that says “Msvsmon started a new server named ‘{Your Computer Name}:4016’ waiting for new connections”. This means that we can now setup our development environment for remote debugging.

Step 2

To setup visual studio just open the project properties page and switch to the debug tab. Here you can change the debug device to ‘Remote Machine’ which will allow you to enter a remote computer name or IP address that will be used as the target when running the application. Once you enter your Surface’s computer name click find to bring up the device selection window.

Remote Debugger

If no device is found then you probably do not have your authentication set correctly on the Surface or you are not on the same network as the other device. Go back to Step 1 and double check both of those items.

Step 3

Now that you have updated the target machine for your project the run button should now say ‘Remote Machine’. Run the application and instead of deploying into your local environment it will send the package over to your surface and start a new debugging session. At this point you can set breakpoints or pause as if it was running locally.

If the package does not deploy check the error code but again it is likely a problem with the authentication option you chose or not having the machines on the same network.


You should be all set now to use your surface to debug your windows 8 store applications. Debugging directly allows for a big increase in productivity and allows you to test how your application will perform on the Arm processors found in your Surface or and other Win RT devices.