Posted 4 August 2017, 2:55 pm EST
We are wondering if using the BinaryWrite method carries a high memory-usage overhead cost.
We have a Classic ASP file that calls report dlls, and if it's going to be streamed to the browser, the dll returns the bytestream to the ASP file, which pushes it to a new browser window.
Otherwise, the dll saves a file to a directory on the web server, returns the path, and the asp just re-directs the user to that file.
It seems that the binaryWrite method is going to cause the bytestream to be held in memory - how is that memory location freed up? Should we be using the other methods where possible?
thanks in advance for your expertise!