C# read zip file into stream

Memory stream, on the other hand, is a bucket. Please give me details on what you're really trying to do. Trying to predict your next question, can I offer the following example which also servers a general demonstration of stream usage? This code opens the file at inPath , obtains the first file in the zip archive, and writes it to outPath.

Note that this uses ZipLib to handle zip files not handled natively by the CLR ; note that at any point in time we are only handling bytes of data, even for a Mb file - so we haven't read the entire file into memory first. We have three streams here; we have connected two "pipes" streams together, with the nifty ZipLib code in the middle, so when you request e.

We then write this amount from the buffer to out output stream. ZipInputStream inFile using System. Flush ; outFile. But as someone once pointed out to me then. NET supports java. This discussion thread is closed Start new discussion. Similar topics. NET Framework.

The method returns a FileStream. The FileStream's Read method reads a block of bytes from the stream and writes the data in a given buffer. The first argument is the byte offset in array at which the read bytes will be placed.

The second is the maximum number of bytes to read. The Encoding. GetString decodes all the bytes in the specified byte array into a string. In the following example, we use FileStream in combination with StreamReader. In the example, we read a text file.

When we use StreamReader , we do not need to do the decoding of bytes into characters. We pass the FileStream to the StreamReader. If we do not explicitly specify the encoding, the default UTF8 is used.

We read the data with the StreamReader's WriteLine method. GetEntry Method String System. Open Method System. Posted Sep am Dave Kreskowiak. Andy Lanng Sep am. A: you didn't read my current solution B: your answer offers me no more information than I gave C: jpeg has compression levels.

You can easily achieve much higher in a zip. Also, each zip file contains hundreds of images to better ratios are likely. Dave Kreskowiak Sep am. Sorry, I missed the code. I fully realize JPG has compression levels. Most are compressed to the point where a ZIP is pointless.

If you've got JPG's that are not compressed as much, lucky you. You're already returning the stream as fast as possible. Since the original ZIP is closed and disposed at the time, the content has to be transferred to another stream that will live long enough. You're only other option to return the content faster is to have the files not in a ZIP but on disk and just have the web server return the file directly by URL.

If space is an issue, try converting the images to a different format and compression. Yes, I know you have "millions" of them. Yeah - That's kinda the conclusion I got to. The images are supposed to be high-res dunno why they chose jpg! Space doesn't have to be an issue. Just adds to the cost.

Dave Kreskowiak Sep pm. I work on a site where we allow users to upload images to be used in documentation. These are normally screenshots, but can be anything.

We had tons of BMP's and they are the worst as they are 32bpp and no compression. After testing on some sets of these images, I found that, in our case, PNG works the best for compressing the images down and without loosing image quality. We have a controller and library that converts any image uploaded in any format to PNG automatically before being shipped off to the database. For good reasons I can't go into, we keep the images stored in the database, not in the server file system.

It's not the most performant way to store the images, but it's what we require. Add your solution here.