StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18571478
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-02T10:53:21.687
FavoriteCount
0
LastActivityDate
2013-09-02T10:53:21.687
LastEditDate
LastEditorUserId
0
OwnerUserId
1893795
ParentId
18566764
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Methods to pass parameters 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: <pre><code>page.NavigationService.Navigate(new Uri("/Views/Page.xaml?parameter=test",UriKind.Relative)); </code></pre> Destination page: <pre><code>string parameter = string.Empty; if (NavigationContext.QueryString.TryGetValue("parameter", out parameter)) { { this.label.Text= parameter; } </code></pre> 2.Using NavigationEventArgs Navigating page: <pre><code>page.NavigationService.Navigate(new Uri("/Views/Page.xaml?parameter=test",UriKind.Relative)); </code></pre> // and .. <pre><code>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.."; </code></pre> Destination page: <pre><code>// Just use the value of "PublicProperty".. </code></pre> 3.Using Manual navigation Navigating page: <pre><code>page.NavigationService.Navigate(new Page("passing a string to the constructor")); </code></pre> Destination page: <pre><code>public Page(string value) {// Use the value in the constructor...} </code></pre> Difference between Uri and manual navigation 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. Passing complex objects 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.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to get values through IsolatedStorage?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGijo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.