StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8117953
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-11-14T06:12:53.927
FavoriteCount
0
LastActivityDate
2011-12-09T12:05:05.323
LastEditDate
2011-12-09T12:05:05.323
LastEditorUserId
381938
OwnerUserId
185859
ParentId
8078169
PostTypeId
2
Score
17
ViewCount
0
LastEditorDisplayName
text
Body
It's not exactly easy, but it's not really that hard either. What you need to do is a spin up a worker Thread that's setup as STA and you start up the Dispatcher runtime on it. Once you have that worker sitting there you can dispatch work to it from the unit test threads which are, obviously, not initialized for this kind of work. So, first, here's how you startup the dispatcher thread in your test setup: <pre><code>this.dispatcherThread = new Thread(() => { // This is here just to force the dispatcher infrastructure to be setup on this thread Dispatcher.CurrentDispatcher.BeginInvoke(new Action(() => { Trace.WriteLine("Dispatcher worker thread started."); })); // Run the dispatcher so it starts processing the message loop Dispatcher.Run(); }); this.dispatcherThread.SetApartmentState(ApartmentState.STA); this.dispatcherThread.IsBackground = true; this.dispatcherThread.Start(); </code></pre> Now, if you want to cleanly shut that thread down in your test cleanup, which I recommend you do, you simply do the following: <pre><code>Dispatcher.FromThread(this.dispatcherThread).InvokeShutdown(); </code></pre> So, all that infrastructure stuff out of the way, here's all you need to do in your test to execute on that thread. <pre><code>public void MyTestMethod { // Kick the test off on the dispatcher worker thread synchronously which will block until the work is competed Dispatcher.FromThread(this.dispatcherThread).Invoke(new Action(() => { // FromCurrentSynchronizationContext will now resolve to the dispatcher thread here })); } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTaskScheduler.FromCurrentSynchronizationContext - how to use WPF dispatcher thread when unit testing
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTim Rogers
UserOwnerUserId
1. USDrew Marsh
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POTaskScheduler.FromCurrentSynchronizationContext - how to use WPF dispatcher thread when unit testing
 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
 VTAcceptedByOriginator
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. COIt worked, thank you very much!
 singulars
 PostPostId
 PO
 UserUserId
 USAlberto

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.