StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1346262
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-08-28T10:48:22.090
FavoriteCount
0
LastActivityDate
2010-08-21T17:05:58.413
LastEditDate
2010-08-21T17:05:58.413
LastEditorUserId
85556
OwnerUserId
85556
ParentId
1339857
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
I finally found out what was the error: it had nothing to do with Soap versions, streams, etc... I just mispelled the name of my own service (!), using <code>FileTransfer</code> instead of <code>FileTransferService</code>. In the end basicHttpBinding was perfectly fine, I didn't need to resort to a custom binding. Original (bad) version: <pre><code><service behaviorConfiguration="serviceBehavior" name="Acme.Service.FileTransfer"> <endpoint address="" name="basicHttpStream" binding="basicHttpBinding" bindingConfiguration="httpLargeMessageStream" contract="Acme.Service.IFileTransferService" /> <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/> </service> </code></pre> New (fixed) version: <pre><code><service behaviorConfiguration="serviceBehavior" name="Acme.Service.FileTransferService"> <endpoint address="" name="basicHttpStream" binding="basicHttpBinding" bindingConfiguration="httpLargeMessageStream" contract="Acme.Service.IFileTransferService" /> <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/> </service> </code></pre> Still I can't say that the error message was helpful in any way to understand what was going on here.... If you are interested in the whole service, you can find more details on my blog at the following link: <a href="http://stefanoricciardi.com/2009/08/28/file-transfer-with-wcp/" rel="noreferrer">File Transfer with WCF</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWCF: using streaming with Message Contracts
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USStefano Ricciardi
UserOwnerUserId
1. USStefano Ricciardi
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWCF: using streaming with Message Contracts
 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. 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.