Defrag Tools: #74 - Windows 8.1 - Frame.GetNavigationState Crash

Download

Right click “Save as…”

  • MP3 (Audio only)
  • MP4 (iPhone, Android)
  • High Quality MP4 (iPad, PC, Xbox)
  • Mid Quality MP4 (Windows Phone, HTML5, iPhone)

In this episode of Defrag Tools, Andrew Richards and Chad Beeder walk you through a common issue in Windows Store applications that use Frame.GetNavigationState. We use a Windows Store 8.1 app sample to show how using complex objects as a parameter in navigation can cause serialization to raise an exception.

Resources:
Frame.Navigate methods
Frame.GetNavigationState
Windows 8.1 Application Samples
Defrag Tools SkyDrive (inc. Scripts and ProcDumpExt)

Timeline:
[00:25]Frame.GetNavigationState
[03:00]Frame.Navigate methods
[03:53] - Parameter must be a char/string/numeric/GUID
[05:42]XAML Navigation sample
[07:00] - Complex parameter works if you don't call GetNavigationState
[09:56] - XAML Frame x:Name
[11:50] - Exception in GetNavigationState
[14:00] - SuspensionManager class
[15:35] - Email us your issues at defragtools@microsoft.com

Tags:

Follow the Discussion

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.