posted to the Microsoft Download Center a Windows Mobile six.5 application improvement kit (SDK) on January 22. Shortly afterward, the business pulled the SDK. are studies that Microsoft may possibly have pulled again simply because the downloadable SDK integrated the Windows Cellular 6.five.three bits. WM 6.five.three is surely an interim model of Windows Mobile that’s been circulating privately for a couple of months. Microsoft officials haven’t made any public pronouncements about WM six.5.three. But according to bloggers bck in December, WM six.five.three adds support for “touchable tiles” instead of soft keys. (According to an entry on Wikipedia, the 6.5.three update also might add more gesture support,
office 2010 pro serial key, a revamped address book and new start menu placement.) has been talk that Microsoft is planning to deliver a edition of Windows Cellular prior to 7.0 that would add full support for capacitive screen phones,
discount win 7 64bit, but,
windows 7 home premium upgrade key, again, no firm officials have confirmed this publicly. (Some have referred to this capacitive release as WM 6.six or 6.7. But maybe it’s six.5.3…) asked Microsoft officials why the WM 6.five SDK was pulled and when it might be back. If and when I hear back, I’ll update this post. A Microsoft spokesperson just provided the following update via e-mail. From the mail,
office 2010 pro plus x86, it sounds like MIcrosoft jumped the gun and inadvertently posted a beta of a six.five.3 SDK: Friday,
microsoft office Home And Business 32 bit, January 22nd Microsoft prematurely posted a version of an upcoming Windows Mobile six.five SDK to a public facing Web page. the SDK was not announced or promoted, it was discovered and generated questions from the community. beta SDK has since been removed and will be reposted once final testing has been conducted. We apologize for any inconvenience.” understand Microsoft wants to maintain an element of surprise about its WM offerings and strategy. But at this point, it seems Redmond’s confusing signals and unwillingness to provide guidance and information regarding its WM roadmap could be doing more harm than good…