Similar questions have been asked before but this question strives to explore more options and the ability to pass complex objects.
The question is how to pass parameters but it really needs to be broken up into three parts..
Example of Uri navigation
page.NavigationService.Navigate(new Uri("/Views/Page.xaml", UriKind.Relative));
Example of manual navigation
page.NavigationService.Navigate(new Page());
The answer to this question applies to WP7, silverlight, WPF and Windows 8.
Note: There is a difference between Silverlight and Windows8
just create an instance of the second page. Pass the value/objects/... into the constructor, and then use Page. NavigationService to navigate to the newly created instance.
WPF uses XAML as its frontend language and C# as its backend languages. WPF was introduced as a part of . NET Framework 3.0 as the Windows library to build Windows client apps and the next generation of Windows Forms.
1. Using the query string
You can pass parameters through the query string, using this method means have to convert your data to strings and url encode them. You should only use this to pass simple data.
Navigating page:
page.NavigationService.Navigate(new Uri("/Views/Page.xaml?parameter=test", UriKind.Relative));
Destination page:
string parameter = string.Empty;
if (NavigationContext.QueryString.TryGetValue("parameter", out parameter)) {
this.label.Text = parameter;
}
2. Using NavigationEventArgs
Navigating page:
page.NavigationService.Navigate(new Uri("/Views/Page.xaml?parameter=test", UriKind.Relative));
// and ..
protected override void OnNavigatedFrom(NavigationEventArgs e)
{
// NavigationEventArgs returns destination page
Page destinationPage = e.Content as Page;
if (destinationPage != null) {
// Change property of destination page
destinationPage.PublicProperty = "String or object..";
}
}
Destination page:
// Just use the value of "PublicProperty"..
3. Using Manual navigation
Navigating page:
page.NavigationService.Navigate(new Page("passing a string to the constructor"));
Destination page:
public Page(string value) {
// Use the value in the constructor...
}
I think the main difference here is the application life cycle. Pages created manually are kept in memory for navigation reasons. Read more about it here.
You can use method one or two to pass complex objects (recommended). You can also add custom properties to the Application
class or store data in Application.Current.Properties
.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With