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.
[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 firstname.lastname@example.org
Available formats for this video:
Actual format may change based on video formats available and browser capability.