Another appropriate way for passing data from one page to another during the navigation is in setting up destination page properties (or variables) within OnNavigatedFrom method of source page.

OnNavigatedFrom method is called just before a page is no longer the active page in a frame. For example this method is called if you invoke NavigationService.Navigate method from a source page. Due to the fact that OnNavigatedFrom method accepts NavigationEventArgs as input parameter you have access to the destination page stored in Content property.

Sample

I have created two pages: Page1.xaml and Page2.xaml. Inside Page2 I have added a string property named Parameter. Inside Page1 (codebehind) I have overridden method OnNavigatedFrom for setting up Page2′s Parameter property.

protected override void OnNavigatedFrom(System.Windows.Navigation.NavigationEventArgs e)
{
    Page2 page2Instance = e.Content as Page2;
    if (page2Instance != null)
    {
        page2Instance.Parameter = "value";
    }
}

Advantages

Probably one of advantages is that you don’t have to store values in static context, but simply pass them from one page to another. That approach is great for a wizard when you have several pages in a row and you need to store only the final result after wizard is completed.

Disadvantages

This approach cannot be applied to applications that can lose sensitive information during the suspend mode (Tombstoning), because when system restores your application from suspend mode there is no way to call OnNavigatedFrom method to set destination page properties.