Windows Mobile Marketplace updated- can install apps to storage cards

Posted by | 02/23/2010 | 2 Comments

Microsoft is trying to get us back to being enthusiastic about the Windows Mobile platform.  First there is the news from MWC about Windows Phone 7, and now there is an update to the Windows Mobile Marketplace.

Users running Windows Mobile 6.x can upgrade to the newest version of the Marketplace.  The updates include  in-depth links to application product pages, user-selectable regional stores, Russian support, and some other changes.  Its a solid upgrade for anyone using a Windows Mobile device.

The most notable piece of the upgrade is the ability to install and run applications from the storage card.  Yes, finally someone is allowing this to happen, without having to root a device or change to a different ROM (yes, I am looking at you Android).  This is a huge boon to Windows Mobile users. Hopefully other companies adopt this piece of the upgrade.

Tags:

Category: Mobile

About the Author (Author Profile)

A 15-year veteran of the tech wars, Amy is a gadgetgrrl from way back. Amy is started with the her first PDA, a Palm Pilot III all the way through her current sidearm, a T-Mobile G1. She suffers technolust like any good gadgetgrrl, but its always tempers with whether it will match her shoes and handbag. She bounces from one device to another. She is an OS agnostic-- liking them all for different reasons. She has seen it all and wants to see more.
  • GoodThings2Life

    To be clear… Windows Mobile has ALWAYS had this functionality. Only the Marketplace initial release neglected to offer the capability, and it’s great that they have resolved the issue.

    It should also be known that not all programs respect the selection… some things are hard coded to only go to internal memory regardless of what you choose.

    • GoodThings2Life

      PS– the latter issue is the result of how the .cab file installers work, not by any inherent issue with Microsoft or the process. Each cab contains an XML file with instructions and file locations. If the vendor hard-codes their file paths to \Windows or similar structure rather than variable paths (%CE#%) then it causes the behavior.

«
»