SharpDevelop Community

Hi, all.

sorry for my poor english, below.

i) on Windows XP sp2(jpn), VS2005, .NetFramework 2.0, and ICSharpCode.SharpZipLib.dll for .Net2.0 v0.85.5.452

ii) get sample from http://www.icsharpcode.net/OpenSource/SharpZipLib/DownloadLatestVersion.asp?what=SourceSamples

iii) use sample:SharpZipLib_0855_SourceSamples.zip::SrcSamples/samples/vb/CreateZipFile

iv) make a zip file. (i'll call this "sample.zip")

v) any tools for Zip can't extract from the "sample.zip". 

open "sample.zip" by  binary-editor, you can find in ZipEntry.ComplessdSize=0xffffffffL (-1)

it means no one can find end of complessed data of a entry.

its a bug?

in SharpZipLib - Release History , Changes for v0.85.5.452

"Bug in entry handling for stored entries and sizing fixed." 

it meanes this? 

it makes this? 

anyone can change #ZipLib?

thanks.

p.s. i'll can read simple english only.

I'll report again.

I found ICSharpCode.SharpZipLibrary.dll v0.84.0.0 at other web-site.

It works very nice in this case.

Hi,

I dont have any such problems.  Using comercial packages I can open, test etc and its all fine.  The sizes are reported fine.  PKUNZIP 2.0 command line says the files are fine.

So I am not sure what you are seeing or why.

NOTE: I am currently targeting .NET 3.5 although I dont see how this will make any difference. The code is no different.

Cheers,

-jr-

> So I am not sure what you are seeing or why.

hmmmm....?

thanks for ur info, anyway.

For what it's worth, I'm having a similar issue with version 0.85.4.369.  Using this version creates corrupt zip files with the published sample code.  The most obvious indication that they are corrupt is that their packed size and size attributes show 4,194,304 KB.  Windows Explorer has problems extracting these zip files as well. 

I'm using VS 2008 and Windows 2003 Server.  Targeting .NET 2.0 or 3.5 makes no difference.  But as HagiMoon indicated, switching the reference to the 0.84.0.0 version of the assembly works just fine with no changes to the client code.  I don't mind using the downlevel version, so just an FYI.

Hi,

Thats not a bug.  Its a problem with Zip64 which windows built in zip handling doesnt know about.

Multiple ways to fix that:

set the size in entries before adding them, or turn off zip64, or dont use windows built in zip handling to try and read the files.

hth, -jr-