开发者

PDF/A Convertor .NET Component? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers. 开发者_如何学Python

Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.

Closed 8 years ago.

Improve this question

I am looking for a PDF/A Converter .NET Component or a way to make one what all technologies of components should be used? Ii would take a word document as as stream and convert it into pdf etc.

Convert word (2003/2007 mostly..and if other office formats etc it would be good.

Convert not create.

Thanks in advance.


Http://www.activepdf.com/


Several options

  • Aspose - Expensive
  • Textcontrol - Very expensive
  • Spire - $800
  • Raster Edge - Very expensive
  • Gembox.Document - $480
  • Subsystems - $550
  • Muhimbi - Expensive and uses Office interop
  • ActivePDF - $400. I think they use Office interop on the server
  • Office Interop - Free, but not supported by M$ and ... just don't.
  • Open Office Interop - Also free. Also scary.

Prices in US$ are current as of January, 2014

What is this interop of which you speak?

Where you install Word or something on the server, include the DLL in your project as a reference and then call methods. Problem is these libraries were not written for multi-user/server/web environments. Almost 100% guaranteed to give you errors.


You could take a look into Aspose.Pdf for .NET


Two questions come to mind:

  1. What is the business case/quantity of Office documents you are translating? Is this a web app that will have hundreds of thousands of users hitting the web server simultaneously, or are you OK with a batch style or to throttle the number of users?
  2. What level of quality do you want the PDF at? Print-quality, or web?
0

上一篇:

下一篇:

精彩评论

暂无评论...
验证码 换一张
取 消

最新问答

问答排行榜