I ran into some zip/deflate trouble tonight you should be aware of.

I have SharpZipLib on the server-side and a licensed C1 zip library on the
Silverlight side. C1 can unzip files from the server, but the other
direction produces unzip corruptions. I'm guessing that someone isn't
obeying the letter of the law, so there's a gotcha.

I noticed this morning that DotNetZip (which I've used before and quite
like) has a Silverlight port, so I thought "great!", the same library on
both sides and no C1 licensing. I ran a quick test and proved that deflated
files could be sent both ways correctly. So I replace the code in the real
app and discover unzip crashes due to IBM437 encoding of file names. I
tested deflate/inflate, but stupidly didn't bother to test zip/unzip and it
crashes. Web searches show other people panicking over this and publishing
fixes. I get the fixed code but it won't build. I spend two hours coaxing
the thing to build and run, but no success.

So sadly more stuff doesn't work and I had to revert everything and wasted
a few hours hard work. The community port of DotNetZip to Silverlight was
subtly and fatally flawed. So take care if you're fiddling this sort of
thing.

Greg

Reply via email to