Tools for working with Office Open XML files

As you all know, the new Office formats use ZIP containers to wrap up all the XML parts that make up a document. We chose to use ZIP and XML because of the wide spread use and openness. While you can use any ZIP library to crack open the files, we are also providing an assembly to make working with the files even easier. Kevin Boske just recently started blogging and he plans to spend some time giving folks a closer look into the System.IO.Packaging functionality. It’s a great way to quickly crack into the ZIP containers and navigate the various parts that make up the files. In his post today, Kevin shows how you can navigate to a specific part within the container.


Comments (6)

  1. Douglas Davidson says:

    Won’t those relationship names be changing post-beta?  The code as shown has them hard-coded.

  2. Yes, the code snippets will need to be updated to match the final relationship types. Same will go for namespaces and content types, but I don’t think Kevin’s example got into either of those.


  3. John Rylander says:

    Particularly given that the current Zip lightweight compression defeats further compression, will there be any option to use alternative compression strategies?  Either using a much higher Zip compression ratio, or using something like WinRAR’s engine instead (the decompression version being free, of course)?  (7zip is also good and is open source, but can be a time and resource hog a bit.)

    The quick Zip compression is at once handy but also annoying for those transmitting large documents or spreadsheets over a limited broadband connection.  (E.g., I sometimes send large spreadsheets–20 MB or more.  When I’ve unzipped them and RARred them, I can quickly reduce that by more than 50%, but it’s a pain both for me [to decompress and recompress] and the recipient [to decompress and recompress].)

    Native higher compression would also be nice for archival storage.

    Ideally, such compression would be built in; as a fallback, at least such decompression could be built in (i.e., presumably no license fee paid by MS, and if they’re smart, RARlabs et al would give you any helpful custom component to do the work gratis).