We expect to learn a lot more about Microsoft's plan to entice developers to Windows Phone 7 at the MIX 2010 developers conference. Until then (March 15-17), aspiring WP7 devs have to rely upon rumor and innuendo to feed their curiosity. So here you go: three purportedly official Microsoft docs from January that provide a glimpse into Microsoft's Windows Phone OS 7.0 Application Platform. First up, the docs claim that WPOS 7.0 is built around Silverlight, XNA (like the Zune HD), and the .NET Compact Framework -- a mostly clean break from WinMo's past as far as developers are concerned. Native apps are restricted to OEMs and mobile operators in order to extend the experience and functionality specific to a phone or network. Even then, they'll be limited to a set of managed APIs that Microsoft will audit during the app submission and provisioning process. Sound familiar?As you'd expect, the OS supports preemptive multitasking -- not that Microsoft will necessarily allow its devs (OEMs, mobile operators, and independent software vendors) to send their apps to the background. The primary development tools include Microsoft's Visual Studio 2010 and Express Blend used in combination with a Windows Phone emulator. Check the docs in the gallery for the full read and be sure to hit up XDA-Developers if you want to commiserate with your like-minded peers.
Gallery: Windows Phone 7 development docs leaked?
Windows Phone 7 development policies and guidelines leaked? originally appeared on Engadget on Thu, 18 Feb 2010 05:56:00 EST. Please see our terms for use of feeds.
Permalink
WMPoweruser | 
XDA-Developers | Email this | Comments 
At this point, there have been so many Sonic games on so many different platforms, that you don't really need to run an old school 
We had a chance to take a tour of Nokia's research and development facility in San Diego this week -- and while we're afraid to say we didn't see any Maemo 6-powered devices or Symbian^4 emulators lying around, we did see some pretty cool stuff, particularly in the product testing laboratories where engineering samples and final products are put through pure hell. The idea is to simulate years' worth of real-life product use in just a few days -- individual tests last anywhere from a few hours to three weeks or longer -- by pressing buttons, sliding sliders, actuating hinges, heating, cooling, wetting, drying, dropping, whacking, shaking, rubbing, bending, and generally defacing the phones in every way imaginable. Once a phone finally breaks, they look for obvious reasons -- cracked plastic, broken springs, and the like -- but if that initial analysis fails, they've got a well-equipped lab on site complete with a scanning electron microscope and CT scanner for taking microscopic looks at failed components in both two and three dimensions; from here, they can find broken connections on chips, incorrectly-fabricated materials, and the occasional ant eye magnified a couple thousand times (it's posted on the wall in the lab, and yes, it's scary). Follow the break for a cheerful montage of a few Nokia phones getting mercilessly beaten beyond recognition.
