a 'mooh' point

clearly an IBM drone

Generation of ODF-files on the .Net-platform

Some time ago I wrote a couple of articles about how to generate ODF-files as well as OOXML-files using .Net technology (both articles are in Danish). For generation of OOXML-files I used the - at that time - new .Net 3.0 System.IO.Packaging assembly and for generation of ODF-files I used AODL - a part of ODF Toolkit.

I thought it was time to refresh my skills - and share them with you guys - since the OOXML/ODF-debate has cooled down to a more relaxing level.

A few weeks back Microsoft released the first production-code edition of their OpenXml SDK - version 1.0. I will dig into this a bit later.

I thought I'd kick this series off with a couple of articles about ODF-file generation on the .Net platform, but I was unpleasantly surprised to realize, that it might not be as easy as it sounded. First, I was told that AODL was a dead project. Surely, the latest addition of code was in April 2007 and it seems that nothing has happened since.  It looks as if the resources of ODF Toolkit is focused on ODFDOM - currently a Java-project. The problem is - AODL seems to be the only .Net-project available. I have stumpled across the ODF .Net project by IndependentSoft, but they sell an ODF library as Closed Source Software ... for (brace yourself) €999 a pop! Seriously - selling CSS-libraries is just sooo 2006 ...

And then I come to you, dear reader ... what the hell do I do? Do you know of other .Net libraries that allow me to create and manipulate ODF-files?



Comments (2) -

Mm, you're out of luck, I'm afraid...

You could consider using OpenOffice.org's UNO components (http://tirania.org/blog/archive/2008/Jun-12.html), but it isn't very .Net-ish and you need OOo...

Hi Bart,

Thanks for your reply - but as you say, the C#-bridge to OOo is not so appealing. One of the advantages of e.g. the OpenXml SDK is that it removes the requirement of having installed Microsoft Office on webservers to create .DOC-files. Of course OOo is much cheaper than Microsoft Office, but from an architectural point of view, having to install OOo on a webserver is the same (bad) thing. If I wanted to create an ODF-reader for e.g. the iPhone, installing OOo to get it to work would also  be quite a challenge.


Comments are closed