If you are following the news around our new technical documentation experience, you probably know that last week we revamped our managed reference experience and launched the .NET API Browser. In today’s post, I thought I would go into the nitty-gritty of the process and talk about how exactly we generate reference documentation for .NET Framework and related managed SDKs.
With the release of Windows Phone 8, a few new developer API endpoints were made available that allow third-party applications to change the device lockscreen image. In this article, I am establishing the infrastructure and building a mobile application that provides the ability to choose from a number of dynamic image sets, from which images can be selected and then cycled as lockscreen wallpapers.
For some situations, the controls that are out there are not enough. That is why I started working on my own control toolkit. As I work on my own applications and feel the need to implement a custom control, I will add it to the Windows Phone Control Kit collection.
The official Kinect SDK is here, so there shouldn’t be any problems with incompatible frameworks and libraries on Windows systems. That being said, there are already a couple of interesting resources that I would say are important for developers who just start Kinect development, and for those that were already working with it (e.g. with OpenNI or OpenKinect).
I found out that the Xbox Live Game Marketplace content is syndicated via a web service tied to the Xbox Live CDN. The service returns enough information to build my own syndication client, which will be able to read game data about various titles that are currently available to be downloaded through the Xbox Live Marketplace. Here, I will explain some details on how exactly the queries can be built.