Click here to Skip to main content
Click here to Skip to main content

C# Use Zip Archives without External Libraries

By , 12 Jun 2011
 

Introduction

I found a lot of articles on how to access Zip archives in C# but all with significant disadvantages. The main problem is that Microsoft has Zip archives implemented in the operating system but there is no official API that we can use. In C# for example, we have the System.IO.Compression.GZip but there is no adequate System.IO.Compression.Zip class.

There are some free .NET compression libraries like SharpZipLib and .NET Zip Library, but this leads to additional installation effort and licensing problems.

It is also possible to use the free J# Library. J# has included Zip to keep compatible with the Java libraries. But to bundle a 3.6 MB DLL vjslib.dll, just to support Zip, seems like a really goofy hack.

Since .NET 3.0, we can use the System.IO.Packaging ZipPackage class in WindowsBase.DLL. It's just 1.1 MB, and it just seems to fit a lot better than importing Java libraries.

Problem only that the ZipPackage class isn't a generic Zip implementation, it's a packaging library for formats like XPS and Office Open XML that happen to use Zip.

To access simple Zip archives with ZipPackage fails because the content is checked for Package conventions.

For example, there has to be a file [Content_Types].xml in the root and only files with specified extensions are accessible. Filenames with special characters and spaces are not allowed and the access time is not the best because of the additional Package link logic.

However, the assembly WindowsBase.DLL is preinstalled and the generic Zip implementation is inside. The only problem is that the generic Zip classes are not public and visible for the programmers. But there is a simple way to get access to this hidden API and I wrote a small wrapper class for this.

Background

A quick check in the Object Browser shows us that WindowsBase.DLL has a namespace MS.Internal.IO.Zip. This sounds good, but there are no public classes visible.

However, the following call:

var types = typeof(System.IO.Packaging.Package).Assembly.GetTypes();

gives us 824 class types, public and non-public and especially one with the name MS.Internal.IO.Zip.ZipArchive. Now it is easy to get this special class type and the methods and properties:

var type = typeof(System.IO.Packaging.Package).Assembly.GetType
		("MS.Internal.IO.Zip.ZipArchive");
var static_methodes = type.GetMethods(BindingFlags.Static | 
		BindingFlags.Public | BindingFlags.NonPublic);
var nostatic_methodes = type.GetMethods(BindingFlags.Instance | 
		BindingFlags.Public | BindingFlags.NonPublic);

and we get the most important methods:

static ZipArchive OpenOnFile(string path, FileMode mode, 
	FileAccess access, FileShare share, bool streaming);
static ZipArchive OpenOnStream(Stream stream, FileMode mode, 
	FileAccess access, bool streaming);
ZipFileInfo AddFile(string path, 
	CompressionMethodEnum compmeth, DeflateOptionEnum option);
ZipFileInfo GetFile(string name);
ZipFileInfo DeleteFile(string name);
ZipFileInfoCollection GetFiles();
void Dispose();

The same procedure for ZipFileInfo and we get:

Stream GetStream(FileMode mode, FileAccess access);

and properties like: Name, LastModFileDateTime, FolderFlag...
This is all what we need to implement a small wrapper class and access over Reflection:

class ZipArchive : IDisposable
{
  private object external;
  public static ZipArchive OpenOnFile
      (string path, FileMode mode, FileAccess access, FileShare share, bool streaming)    
  {
    var type = typeof(System.IO.Packaging.Package).Assembly.GetType
		("MS.Internal.IO.Zip.ZipArchive");
    var meth = type.GetMethod("OpenOnFile", BindingFlags.Static | 
		BindingFlags.Public | BindingFlags.NonPublic);
    return new ZipArchive { external = meth.Invoke(null, new object[] 
		{ path, mode, access, share, streaming }) };
  } 
  //...
  public class ZipFileInfo //...
}

The complete ZipArchive wrapper implementation is in the demo project ZipArchiveTest in Program.cs.
Only 97 lines for this class and we can use it in a code sequence like this:

var str = new MemoryStream();

//create some files:
using (var arc = ZipArchive.OpenOnStream(str))
{
  var doc1 = new XDocument(new XElement
	("root", new XElement("item"), new XElement("item"), new XElement("item")));
  var doc2 = new XDocument(new XElement("root", Enumerable.Repeat
		("item", 1000).Select(p => new XElement(p))));
  using (var fs = arc.AddFile("test1.xml").GetStream
		(FileMode.Open, FileAccess.ReadWrite)) doc1.Save(fs);
  using (var fs = arc.AddFile("test2.xml").GetStream
		(FileMode.Open, FileAccess.ReadWrite)) doc2.Save(fs);
}

// read the files:
using (var arc = ZipArchive.OpenOnStream(str))
{
  var doc1 = XDocument.Load(arc.GetFile("test1.xml").GetStream());
  var doc2 = XDocument.Load(arc.GetFile("test2.xml").GetStream());
  var doc3 = XDocument.Load(arc.GetFile("dir/test3.xml").GetStream());
}

Using the Demo

The demo program ZipArchiveTest using the ZipArchive class is as small as possible and can show the content of Zip archives without any restrictions. Double click to files in the ListBox opens a new window to show the file content as text.

Conclusion

Microsoft should publish its hidden ZipArchive class, but till then, we can use such a simple wrapper to save terabytes of data worldwide.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

About the Author

D. Christian Ohle
Germany Germany
Member
No Biography provided

Sign Up to vote   Poor Excellent
Add a reason or comment to your vote: x
Votes of 3 or less require a comment

Comments and Discussions

 
You must Sign In to use this message board.
Search this forum  
    Spacing  Noise  Layout  Per page   
GeneralThanks! High 5 DudememberAwchie13 Nov '12 - 15:21 
I really need a file zipper that does not use third party libs (to not become their %!$@&). Thanks for the article!
GeneralMy vote of 5membergelo_one12 Nov '12 - 23:07 
Good!
GeneralThanksmemberTheGrandBazaar12 Nov '12 - 4:21 
This is very useful for people not working with .NET 4.5 and who
don't want to use third party libraries.
GeneralMy vote of 5memberElron022 Nov '12 - 13:28 
exactly what i wanted! Thank you.
GeneralMy vote of 5memberCollin Heine21 Sep '12 - 7:57 
I've been looking for some kind of guidance like this forever! Thanks!
GeneralMy vote of 5memberMark Lemke12 Sep '12 - 0:57 
It seems that I forgot to vote. This article is very useful, especially since I can't upgrade to .NET 4.5 and don't want to use a third party solution for multiple reasons.
QuestionNo file compression ??memberBillJam119 Aug '12 - 8:25 
Am I missing something? I get the code here to work and create a zip file and add files to it but they are all uncompressed even though I'm specifying Deflated for the compression option and Normal for the Deflate option (yes, I tried Maximum here also).
Anyone?
AnswerRe: No file compression ??memberBillJam119 Aug '12 - 8:49 
And I new it had to be something stupid. My test files were already compressed - didn't know that.
QuestionProblem with non ascii characters in file names [modified]memberNyarlatotep18 Jun '12 - 7:45 
This is an useful class.
 
However, a strange problem arises when file names added (AddFile) to the zip folder, contain non ascii characters (accented characters, by the way).
The zip archive seems to contains all the files, but if I try to open that zip with windows explorer, those files are not shown in the archive list.
Opening the archive with 7zip, shows all the files but accented letters are replaced with question marks.
Could it be a problem with WindowsBase/Reflection non supporting unicode strings (it sounds weird, anyway)?
 
Thanks

modified 18 Jun '12 - 13:55.

AnswerRe: Problem with non ascii characters in file namesmemberD. Christian Ohle19 Jun '12 - 6:54 
Hello Nyarlatotep
you are right, I could reproduce it with a filename like "é.txt".
But it is no problem with Reflection.
Internal the MS...ZipArchive has a field _blockManager._encoding and this is as Type fixed to System.Text.ASCIIEncoding.
It means we can not change the encoding.
It seems to be a limitation, but there is always a way, unfortunately I found nothing.
Would be interesting if someone has an idea.
Regards
Christian

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Permalink | Advertise | Privacy | Mobile
Web02 | 2.6.130523.1 | Last Updated 12 Jun 2011
Article Copyright 2011 by D. Christian Ohle
Everything else Copyright © CodeProject, 1999-2013
Terms of Use
Layout: fixed | fluid