VisualStudioFeeds

All Visual Studio blogs in one place

AddThis Social Bookmark Button
One of the challenges that confronts every Windows phone developer is learning about tombstoning. As I briefly stated in an earlier article, tombstoning is Windows Phone 7’s way of allowing an application to restore itself to the same state it was in before it was interrupted. Although the operating system itself can run several applications at once, for performance reasons, applications written by you, me, and other non-OEMs are only allowed to run one at a time. If an application is running and it launches the phone’s Web browser to display a Web page, the app is tombstoned
until the user presses the Back button to exit the browser. Once the app is reactivated (that is, if it’s reactivated – there’s no guarantee the user will press the Back button), it’s the app’s responsibility – not the operating system’s – to restore itself to its previous state before resuming execution. No app is required to support tombstoning, but users won’t care much for apps that lose their work just because they launched a browser or performed some other benign task. And such apps probably wouldn’t be approved for the Marketplace, anyway. Of course, launching a browser isn’t...(Read whole news on source site)

Search

Subscribe

Enter your email address:

Delivered by FeedBurner

Increase your website traffic with Attracta.com

Contact

Email:
Subject:
Message:
Anti-spam: How many eyes has a typical person?

Follow us on FB

Home : Blog List : Jeff Prosise's Blog : Real-World Tombstoning in Silverlight for Windows Phone, Part 1