StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19005775
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-09-25T13:05:25.947
FavoriteCount
0
LastActivityDate
2013-09-25T13:05:25.947
LastEditDate
2017-05-23T12:31:41.293
LastEditorUserId
-1
OwnerUserId
1404233
ParentId
19005401
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You don't want to reference UI elements by name in the code-behind. Actually any time you can avoid naming an object you <a href="https://stackoverflow.com/questions/3100007/not-specifying-control-names-in-wpf-performance-effect">save a little in performance</a>. And by setting up your app to use MVVM properly, you gain in performance, readability, maintainability, and code separation. You want to abstract things further to use the MVVM pattern. You're doing your bindings correctly but consider the pattern. Your view is all correct. Consider adding a class that holds the properties defined currently in your code-behind and the methods called in your event handlers. <pre><code>public class ViewModel : INotifyPropertyChanged { private FunctionalTester _funcTester; public FunctionalTester FuncTester { get { return _funcTester; } set { _funcTester = value; OnPropertyChanged( "FuncTester" ); } } public async void TestAsync( ) { await _funcTester.Test( ); } } </code></pre> A binding to the FuncTester would simply be <code>SomeProperty="{Binding FuncTester}"</code> because the object is set as the DataContext of your view. A decent article that expands on this idea <a href="http://msdn.microsoft.com/en-us/magazine/dd419663.aspx" rel="nofollow noreferrer">is found here</a>. Obviously left out some things (like <a href="http://msdn.microsoft.com/en-us/library/system.componentmodel.inotifypropertychanged.aspx" rel="nofollow noreferrer">INotifyPropertyChanged</a> implementation and other properties you've defined) for brevity. But just make this class and assign it as your view model. Then the UI (the Xaml and the code-behind) only really deal with the UI and the ViewModel really deals with the data and logic. Great separation. For your event handler, just call <code>((ViewModel)this.DataContext).Test( );</code> and you can plug-and-play your ViewModel's to change functionality on the fly. Hope this helps!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POProper Code-Behind Object Data Binding in XAML?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USWill Custode
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. COHow exactly do I set your ViewModel object as the DataContext for the GroupBox/View? I guess that's where i'm a bit confused.
 singulars
 PostPostId
 PO
 UserUserId
 USYnotDraw

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.