StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8184960
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-18T15:43:27.107
FavoriteCount
0
LastActivityDate
2011-11-18T15:43:27.107
LastEditDate
LastEditorUserId
0
OwnerUserId
1027808
ParentId
1854409
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
To determine the actual order that the code executes in I would recommend turning on Tracing for WCF and look over the generated trace logs. This can be enabled by adding this to the config file: <pre><code><configuration> <system.diagnostics> <sources> <source name="System.ServiceModel" switchValue="Information, ActivityTracing" propagateActivity="true"> <listeners> <add name="traceListener" type="System.Diagnostics.XmlWriterTraceListener" initializeData= "c:\log\Traces.svclog" /> </listeners> </source> </sources> </system.diagnostics> </configuration> </code></pre> As far as the extensibility points in WCF, Carlos Figueira (one of the engineers of WCF at Microsoft) has a post detailing almost all of the extensibility points in WCF ( <a href="http://blogs.msdn.com/b/carlosfigueira/archive/2011/03/14/wcf-extensibility.aspx" rel="noreferrer">http://blogs.msdn.com/b/carlosfigueira/archive/2011/03/14/wcf-extensibility.aspx</a> ). In the WCF Runtime section of this post the ordering is listed as such: <pre><code>1.2. WCF Runtime 1.2.1. Message interception 1.2.1.1. I[Client/Dispatch]MessageInspector 1.2.1.2. IParameterInspector 1.2.2. Mapping between message and operation parameter 1.2.2.1. I[Client/Dispatch]MessageFormatter 1.2.3. Mapping between message and CLR operations 1.2.3.1. I[Client/Dispatch]OperationSelector 1.2.3.2. IOperationInvoker 1.2.4. Instance creation 1.2.4.1. IInstanceProvider 1.2.4.2. IInstanceContextProvider 1.2.5. Error handling 1.2.5.1. IErrorHandler 1.2.6. Others 1.2.6.1. ICallContextInitializer 1.2.6.2. IChannelInitializer 1.2.6.3. IInteractiveChannelInitializer </code></pre> I think between the two the order of operations in WCF should become clear.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat is WCF dispatch pipeline message flow
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPhil Patterson
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. 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.