Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think you can't transfer in the message body a Stream and another data. You need to use a MessageContract to add custom data in the header of the message, and the stream in the body.</p> <p>You need to use a specific contract. You can use class with messagecontract which encapsulate your current contract. Like this :</p> <pre><code>[ServiceContract] public interface IFileDownloadService { [OperationContract] StreamResponse DownloadFile(DownloadFileCommandRequest command); } [MessageContract] public class StreamResponse { [MessageHeader()] public CommandResult&lt;FileDownloadDTO&gt; {get; set;} [MessageBodyMember(Order = 1)] public Stream FileByteStream { get; set; } } [MessageContract] public class DownloadFileCommandRequest { [MessageBodyMember(Order = 1)] public DownloadFileCommand FileCommand {get; set;} } </code></pre> <p>And remove the stream property in FileDownloadDTO class. Maybe if you only remove the DataMember attribute it's ok.</p> <pre><code>[DataContract] public class FileDownloadDTO : IDisposable, IDTOBase { [DataMember] public string FileName { get; set; } [DataMember] public long Length { get; set; } [DataMember] public int Id { get; set; } } </code></pre> <p>Here, an exemple of the client configuration.</p> <pre><code>&lt;binding name="FileHttpBinding" closeTimeout="04:01:00" openTimeout="04:01:00" receiveTimeout="04:10:00" sendTimeout="04:01:00" allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard" maxBufferSize="2147483647" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647" transferMode="Streamed" messageEncoding="Mtom"&gt; &lt;readerQuotas maxDepth="128" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" /&gt; &lt;security mode="None"&gt; &lt;/security&gt; &lt;/binding&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PO(Another) The remote server returned an unexpected response: (400) Bad Request - Castle Windsor, WCF
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USHyralex
    1. USHyralex
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis is 100% correct, I need to update my question to reflect these changes that were made yesterday after some more reading. However, I am still geting the same error even when using the MessageContracts. As far as I can tell it is a problem with the bindings and configuration of Windsor. +1 for correct-ness though, however the problem still remains.
      singulars
      1. PO
      1. USM05Pr1mty
    2. CO@M05Pr1mty I don't think the configuration is the problem, because I have the same and it works. Try, to simply your contract and see if it the problem. Maybe the message header is too complex. Try to remove the generic type CommandResult<>. I edited my response to put an exemple of my client configuration.
      singulars
      1. PO
      1. USHyralex
    3. COupdated question with some comments, and current state of code. Cheers for the help.
      singulars
      1. PO
      1. USM05Pr1mty
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload