When answering a question please: • Read the question carefully. • Understand that English isn't everyone's first language so be lenient of bad spelling and grammar. • If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Chronicle Of Two Losers Rar.

Insults are not welcome. • Don't tell someone to read the manual.

We are trying to build a web service that can send/receive large data files from kb. Send Large Data with WCF without. Code of transfering with chunk of. TCP File Transfer in WCF. If your service writes the data to a file or can work with it in smaller chunks. And I'm not trying to trasfer a large file but a.

Chances are they have and don't get it. Provide an answer or move on to the next question. Let's work to help developers, not make them feel stupid.

I'm using WCF and want to upload a large file from the client to the server. I have investigated and decided to follow the chunking approach outlined at However, this approach (just like streaming) restricts the contract to limited method signitures: [OperationContract(IsOneWay=true)] [ChunkingBehavior(ChunkingAppliesTo.InMessage)] void UploadStream(Stream stream); The sample uses the rather convenient example of uploading a file from a fixed path and saving it to a fixed path on the server. Therefore, my question is how do I pass additional parameters to specify things like filename, filepath etc.

I would like something like: [OperationContract(IsOneWay=true)] [ChunkingBehavior(ChunkingAppliesTo.InMessage)] void UploadStream(Stream stream, String filePath); Thanks in advance, Mark. Explains how to use the MessageHeader attribute to force things to be passed in the header, and therefore not count as a parameter. So, instead of passing a stream and other meta data, create a class that has the attribute MessageContract and mark all of the meta data as a MessageHeader. Then, mark the stream as a MessageBodyMember (which the article incorrect calls 'MessageBody'). Have your UploadStream method take a single parameter whose type is that of the MessageContract class you've just created. I've done this successfully, but I haven't done it in tandem with chunking.

You could make your service session-ful and have an initialization method in the contract with the IsInitiating property set to true. Something like: [OperationContract(IsInitiating = true)] void InitializeUploadService(string filename); [OperationContract(IsOneWay = true, IsInitiating = false)] [ChunkingBehavior(ChunkingAppliesTo.InMessage)] void UploadStream(Stream stream); I have never tried it with streaming services but it should basically make WCF enforce that InitializeUploadService is always called before UploadStream. More documentation can be found here.