views:

338

answers:

3

Hi, I been trying to find an Free/Open Source XML-FO processor that i could use in .NET applications but i havent had luck finding one. Do anyone know of one that i could use?

Thanks in advance.

+2  A: 

You can call apache fop from .net

This guy posted some info on getting it to work.

I'm sure a little more searching and you could get some better/more examples.

aintnoprophet
I found this article that comments about a .NET component called nFOp which is a .Net port from the Apache XML Project's FOP Java source. Il be doing some test and see how it does. Thanks Again.URL of article:http://alainrivas.blogspot.com/2008/10/aspnet-xsl-fo-nfop-web-hosting.html
Sherlack
Oh...i totally forgot about nFOP...one of the guys i work with used that.
aintnoprophet
I found another .NET component called fonet , u can find more info at: http://fonet.codeplex.com/. This seem good component.
Sherlack
I test yesterday the nFOP xml-fo component for .net it worked perfectly. Tho i dont like much it depends on some J# .net libraries but it works well.
Sherlack
Thanks for the heads up on fonet.
aintnoprophet
A: 

You can use nfop which is a .NET port of Apache's fop.

You can find it at http://sourceforge.net/projects/nfop/.

Some of it's limitations are:

  • It doesn't support FO 2.0
  • It can only run on 32-bit servers (because it requires a J# SDK be installed)
  • The image support is not always reliable (doesn't support .gif urls but does as file paths)
  • Some of the padding and margin attributes don't always render

As a starter tool it's great. It does the simple formatting that you might expect to be able to do. If you want to do fancy PDf stuff like bookmarks and table of contents, you will probably need to upgrade to professional FO processor.

Good info, thanks!
Sherlack
+2  A: 

There is a free XSL-FO processor for .NET called FO.NET.

I'm using it and it works just fine for my needs.

[EDIT] Sorry, just noticed someone else had already made a comment about FO.NET...

Cocowalla
Uhm, nope, you're the only one. And I would recommend this above the implementations that require VisualJ# to be installed. FO.NET is written in C#. So +1 for you.
Peter