Redmond Diary

By Andrew J. Brust

Blog archive

WinMo's Demise: Notifying Next of "Kin"

This past Monday, April 12th, Visual Studio 2010 was launched. And on that same day, Microsoft also launched a new line of mobile phone handsets, called Kin. The two product launches are actually connected, but only by what they do not have in common, and what they commonly lack.

On the former point: VS 2010 had released to manufacturing a couple weeks prior to its launch. The Kin phones, meanwhile, are not yet available. We don't even know what they will cost. (And I think cost will be a major factor in Kin's success... I told ChannelWeb's Yara Souza so in this article.)

What do the two products both lack? Simple: Windows Mobile 6.x. For example, Kin seems to be based on the same platform as Windows Phone 7 (albeit a subset). And VS 2010 does not support .NET Compact Framework development, which means no .NET development support for WinMo 6.x and earlier.

So I guess April 12th marks Windows Phone "clean slate day." If you want to develop for the old phone platform, you will need to use the old version of Visual Studio (i.e. 2008). Luckily VS 2010 and 2008 can be installed side-by-side. But I doubt that's much consolation to developers who still target WinMo 6.5 and earlier.

Remember, WinMo isn't just about the phone. There are all sorts of non-telephony mobile devices, including ruggedized Pocket PC-style instruments, bar code readers and shop-floor-deployed units that don't run Windows Phone 7 and couldn't, even if they wanted to.

Where will developers in these markets go? I would guess some will stick with WinMo 6.x and earlier, until Windows Phone 7 can handle their workloads, assuming that does indeed happen. Others will likely go to Google's Android platform.

For OEMs and developers who need a customizable mobile software stack, Android is turning out to be out-WinMo-ing WinMo. As I wrote in this post, Google took Microsoft's model (minus the licensing fees) and combined it with a modern SmartPhone feature set (rather than a late 90s/early oughts PDA paradigm), to great success. You might say Google embraced and extended.

You might also say Microsoft shunned and withdrew


Posted by Andrew J. Brust on 04/19/2010 at 1:15 PM

comments powered by Disqus


  • How to Do Machine Learning Evolutionary Optimization Using C#

    Resident data scientist Dr. James McCaffrey of Microsoft Research turns his attention to evolutionary optimization, using a full code download, screenshots and graphics to explain this machine learning technique used to train many types of models by modeling the biological processes of natural selection, evolution, and mutation.

  • Old Stone Wall Graphic

    Visual Studio Code Boosts Java Dependency Viewer

    Easier management of project code dependencies and improvements to extensions for popular Java frameworks and runtimes highlight the February update to Java in Visual Studio Code functionality.

  • Blule Squares

    Visual Studio 2019 for Mac 8.5 Preview Adds ASP.NET Core Authentication

    Microsoft, after shipping Visual Studio 2019 for Mac v8.4 with support for ASP.NET Core Blazor Server applications last month, is now previewing the v8.5 series, adding new authentication templates for ASP.NET Core along with other improvements.

  • Q&A with Brice Wilson: What's New in Angular 9

    We caught up with expert web developer/trainer Brice Wilson to get his take on Angular, which always appears at or near the top of periodic rankings of the most popular JavaScript-based web development frameworks.

  • Entity Framework Core Migrations

    Eric Vogel uses code samples and screenshots to demonstrate how to use Entity Framework Core migrations in a .NET Core application through the command line and in code.

.NET Insight

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.

Upcoming Events