We’re removing tighten to being finished with the OS apportionment of the growth cycle for the arriving Windows Phone release, codenamed ‘Mango!’ ‘Mango’ comes with poignant ultimate functionality for developers. This expansion of the focus height equates to that there have been a little cases in that existent APIs do not work in the same way.
Microsoft is a developer focused company; we have a clever convention around the judgment of focus compatibility. We put a vast volume of bid in to ensuring that all existent WP 7 applications and games run as approaching on ‘Mango.’ That’s not to contend the passing from one to another will regularly be wholly seamless, though. There have been sure classes of issues that have been not simply receptive to a height turn fix. There competence be alternative corner cases that we did not locate in the harmony testing.
Thus it is critical that developers who have published applications in Windows Phone 7.0 exam those applications in Windows Phone Mango.
We’ve done this easy. You can download the ultimate collection for Windows Phone Mango here, and if we have been a Marketplace purebred developer, we will have perceived an call in to refurbish your personal sell device with a pre-release set up of Windows Phone ‘Mango,’ (more info here).
We will be documenting all of the pass API and height changes in abyss on the MSDN Library, (Windows Phone and Silverlight for Windows Phone sections). The Silverlight group is additionally posting currently about focus compatibility, here. I’d similar to to stress the following 3 pass points:
Memory usage. We have a acceptance sequence that states that your app contingency not devour some-more than 90 MB of RAM, on inclination that have 256 MB of RAM or less, (Sec. 5.2.5, accessible here). We have seen cases where people have been checking on the volume of sum RAM, and regulating mental recall in a extravagantly unlimited approach if the series is > 256.
In ‘Mango,’ the mental recall form of the device will be protracted by changes in (a) how we tombstone, and (b) the enablement of credentials agents. It’s critical that your mental recall use be courteous and judicious. Our ultimate graphical profiler is undiluted for assisting we get ahead this.
Web Browser Control. Developers adore the Web Browser Control; the immobile research suggests that > 60% of the developers have been regulating the Web Browser Control in their Windows Phone apps as a arrangement covering at a little point.
In Windows Phone Mango, we have been changeable from IE7 to IE9. This impacts the core HTML, JS, and CSS doing opposite the complete OS. It will additionally stroke we in the use of the Web Browser Control. We’ve seen a little applications knowledge worry in situations where assumptions were done about the sequence in that events get fired.
Silverlight Listbox and WebClient Controls. Both Listbox and WebClient have been reworked and extended in Mango to drastically urge the developer and finish user knowledge compared with these controls. The Silverlight Performance group has created eloquently about these changes on their blog here, (ListBox) and here, (WebClient), and these changes have impacts on existent apps. If you’ve used these classes, greatfully check out these articles for some-more information.
We put this simple list together to assistance we mark a little of the tip focus harmony issues we competence face. There is a lot some-more to optimizing for ‘Mango’. We’ve published utterly a couple of resources already to assistance we get started; in the entrance weeks we’ll be on condition that we even some-more specific superintendence on how to add ‘Mango’ tree nymph dirt to your apps.
Larry Lieberman, Product Manager
Windows Phone Application Platform
* ‘… though were fearful to ask’
