Beware that System.IO.Compression before 4.5 can only deflate/inflate streams, and although the two provided algorithms are standards, I never dared use them outside of the boundary of a single app. From 4.5 you get ZIP support.
I am currently using free SharpZipLib on the server side on combination with costly ComponentOne C1Zip class on the Silverlight client side. I have found that server to client works correctly, but in the other direction I have received decompress errors which hints at subtle and treacherous incompatibilities. I spent hours trying to get SharpZipLib to compile for Silverlight but gave up in tears and had to use C1Zip. To confuse matters there is also Ionic.Zlib which I found years after SharpZipLib and I actually prefer it these days because of a clearer API with some nice convenient high-level methods. I also managed to compile Zlib for Silverlight quite easily and I'm using it both sides of another Server-Silverlight app pair. Of course I feel much safer using the same library on both sides and wouldn't expect incompatibilities like previously mentioned. Greg On 4 October 2013 09:16, David Kean <[email protected]> wrote: > System.IO.Compression namespace.**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *[email protected] > *Sent:* Thursday, October 3, 2013 4:11 PM > *To:* ozDotNet > *Subject:* compression library**** > > ** ** > > Anyoe suggest a library to compress/decompress byte data?**** > > ** ** > > Anthony**** > > Melbourne StuffUps…learn from others, share with others!**** > > http://www.meetup.com/Melbourne-Ideas-Incubator-Stuffups-Failed-Startups/* > *** > > > > ---------------------------------------------------------------------------------- > NOTICE : The information contained in this electronic mail message is > privileged and confidential, and is intended only for use of the addressee. > If you are not the intended recipient, you are hereby notified that any > disclosure, reproduction, distribution or other use of this communication > is strictly prohibited. > If you have received this communication in error, please notify the sender > by reply transmission and delete the message without copying or disclosing > it. (*13POrtC*) > > ----------------------------------------------------------------------------------- > **** > > ** ** >
