Oct 18, 2013 I wrote an app that allowes users to upload files from the browser and send the contents as byte[] to a windows (not IIS) hosted WCF service. TCP File Transfer in WCF. F Zero Gx Iso Ntsc Jobs. NET Framework. One thing that I notice and maybe could help to figure this out is when I send a large file by wsHttpBinding. How To Enable Audio Device Windows 10.

I have a WCF Service that returns a byte array with a Zip file (50MB) to any client that requests it. If the Zip is very small (say 1MB), the SOAP response is coming from WCF with the byte array embedded in it. But the response size is very huge even for a 1MB file. Download Ati Windows Gamer Edition X64 Android here. If I try to transfer the 50MB file the service hangs and throws an out of memory exception, because the SOAP response becomes huge in size. • What is the best option available with WCF / web service to transfer large files (mainly ZIP format) as I am sending back a byte array.

Is there any good approach instead of that for sending back the file? • Whether WCF / web service is best way to transfer large files to any client or is there any other better option/technology available so that interoperability and scalability for 10,000 users can be achieved? My Ccode is below: String pathfordownload = @'D: New Folder.zip'; FileStream F2D = new FileStream(pathfordownload, FileMode.Open,FileAccess.Read); BinaryReader binReader = new BinaryReader(F2D); binReader.BaseStream.Position = 0; byte[] binFile = binReader.ReadBytes(Convert.ToInt32 (binReader.BaseStream.Length)); binReader.Close(); return binFile; A working piece/real piece of information will be really helpful as I am struggling with all the data available in Google and have had no good results for last week. I've faced the exact same problem. The out of memory is inevitable because you are using Byte arrays. What we did is to flush the data on the hard drive, so in stead of being limited by your virtual memory your capacity for concurrent transactions is the HD space.