StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20018135
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-16T11:56:03.307
FavoriteCount
0
LastActivityDate
2013-11-16T13:41:29.613
LastEditDate
2013-11-16T13:41:29.613
LastEditorUserId
2594263
OwnerUserId
590088
ParentId
20017661
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
<pre><code> x:Key </code></pre> Is used when you need to define an element in a ResourceDictionary . For example : a Style or some element you wan't to initalize in xaml . <pre><code> <Style TargetType=Button x:Key="MyBtnStyle> ...... <myLocalNs:MyType x:Key="MyType1" /> </code></pre> . <pre><code> x:Name </code></pre> Would be used when you wan't to eather reference an element from Your Code Behind : <pre><code> <UserControl> <Grid x:Name="grid"> <Button x:Name="btn" /> </Grid> </UserControl> </code></pre> in the UserControl.cs : <pre><code> btn.Contnent = "Im A Button"; grid.RowDefenitions.Add(new RowDefenition()); </code></pre> another case where you would use x:Name is when targeting an element in a ControlTemplate / DataTemplate / Style through Triggers , using TargetName For Example : <pre><code><DataTemplate DataType="{x:Type h:HierarchicalNode}"> <Grid> <CheckBox x:Name="chkbox" /> </Grid> <DataTemplate.Triggers> <DataTrigger Binding="{Binding HasChildren}" Value="False"> <Setter Property="Visibility" Value="Collapsed" TargetName="chkbox"/> </DataTrigger> </DataTemplate.Triggers> </DataTemplate> </code></pre> Another case is when you would wan't to bind to an element in XAML . <pre><code> <UserControl> <Grid x:Name="grid"> <Button x:Name="btn" Content="{Binding ElementName=grid ,Path=Name}"/> </Grid> </UserControl> </code></pre> FYI , x:Name would also be used when you want to Target elements using Interaction Triggers or VisualState's .
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POApplying x:key and x:Name
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USNikhil Prajapati
UserOwnerUserId
1. USeran otzap
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POApplying x:key and x:Name
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.