Aspose.Total for .NET 리뷰

평균 리뷰 스코어: 5 (23)

5 등급에서 5

5 등급
4 등급
3 등급
2 등급
1 등급

가장 최근의 긍정적인 리뷰

Chokchai Lertratanakul태국5 등급

I had been trying create an application to sign digital signature to Office documents and, optionally convert them to PDF. I tried many different libraries (both free and commercial), but they did not... 더 읽기

가장 최근의 중요 리뷰

이 제품에 대한 부정적인 리뷰가 없습니다.
Chokchai Lertratanakul태국5 등급

I had been trying create an application to sign digital signature to Office documents and, optionally convert them to PDF. I tried many different libraries (both free and commercial), but they did not have features that I need (e.g. signing digital signature on Microsoft Signature Line, finding objects in Office documents, etc.). When I found Aspose.Total for .NET, I was able to finish my development within a week. This is a fantastic library for manipulating all kinds of documents.

gautam mehta인도5 등급

We operate a web app which requires end users to upload one or more files, which are then compiled into a single PDF. We need to support a wide range of file types – Microsoft applications plus images and PDFs. We tried Aspose because we were building a new conversion application and we needed a tool which offered functionality which is missing from our current implementation:

  • Faithful reproduction of document layouts (e.g. retaining the layout of entire Excel sheets rather than splitting them across several A4 pages)
  • Retaining tracked changes and comments in Microsoft documents
  • Retaining notes and comments in PDFs
  • Converting MS documents with external data
  • Support for a wide range of file types

We built a proof of concept with the Aspose trial and are pleased to say that it has met all these requirements. It was easy to implement and supports wide variety for .NET frameworks which give us future stable options to migrate as per our needs.

이름 보류 구매하신 고객님슬로베니아5 등급
이름 보류 구매하신 고객님미국5 등급
mamtaaIL, USA5 등급

We have tried Aspose.Words for .NET libraries and the richness of supported file format is very impressive. Additionally, the performance is beyond my expectation comparing to other commercial products out there. The Word files generated by our application are not only created faster, they are more like what our customer's want.  It also has easy to understand interface so that I can integrate to our application without too much difficulty.

We have changed our process in order to eliminate Microsoft Word software dependance forced by the native Interop libraries. With the Aspose library we were able to manage all the process in memory and manage the document more efficiently. The objective is double :

  1. Avoid the installation of Microsoft Word on a server for automation purposes
  2. Better performance with a library directly in a code

Also, Aspose has a complete Microsoft Office library and is very useful to add some flexibility and functionality to our web application. Your mileage will vary depending on the methods used to process documents in regards to integrating their library, but they are functionality complete and the documentation is an integral part of the provided product.

Robert Gransson5 등급

I highly recommend the Aspose product family. It covers almost any need and feature one can have related to documents The company seems to be delivering constant updates and keeping in time with the rest of the technology world (by looking at their twitter feed and newsletters). But the biggest point is the time savings for my project, having just one set of APIs to relate to, makes this a money saver for me.

We needed to read common document formats (PDF, DOCX), extract text from them, save & recompress them as PDFs. (This includes OCR of images, possibly extracted from PDFs) We had to do this to an initial batch of about 200.000 - 500.000 docs, then at a more moderate pace. Three components (Aspose.Words, Aspose.PDF, and Aspose.OCR) would cover the needs, but buying the entire package costs just slightly more than those products separately, and the additional features adds value to my project (spreadsheets, email, imaging, barcode).

Setting up the Aspose products is as easy as: 1) acquiring a license; 2) include the dependencies in your project; and 3) instantiate a component license class and set the license file (which can be done with a memorystream if you don't use file-storage). Aspose has a great documentation of the products that covers the entire API, and common use cases with examples.

The OCR results have been satisfying, we have compared it to Google's open source project Tesseract, and on regular-text-sized documents it gives us good results. Compared to the overhead of having a separate component of doing the OCR, and the "unknown" of using projects that possibly can be abandoned, I prefer the Aspose product.

Finally, Aspose.PDF can handle so-called *iref-streams*. It’s a feature of pdf documents above version 1.4 and is a MUST if you need to read PDFs produced in modern times. (It certainly was a "must have" feature for us!) Many competing products don’t offer this. It’s very easy to glance over requirements or take them for granted. For example, if a component can read document format "X" it does NOT mean that it can write format X, or convert from format X to Y. This is a problem that I haven't found with Aspose products.

thomas.gibbsUnited Kingdom5 등급

Previously, we’ve produced Office Open XML documents directly using the Open XML SDK, which meant having to keep track of various parts of the document that didn’t need changing! That approach meant dealing with things like string tables and needed an intimate knowledge of the internal structure of an Office Open XML document – not something I wanted to get too deep into. There were also a number of issues around memory footprint which resulted in a move to an even more difficult to manage phased export of the different portions of the document.

Using Aspose has been a completely different experience. Aspose.Words allows content to be added to documents using a single method call. The stateful tracking of the styles applied to a paragraph allows for easy styling of multiple paragraphs without keeping track of style references. The insert HTML feature provides straight-forward support for HTML content that has been supplied by end users. The large number of formats that can be saved with just the switch of an enum parameter makes the whole implementation extremely flexible both for us as developers and the end users.

Aspose.Slides makes it easy for us to support user-provided templates by opening existing documents and cloning content from them. Layout slides, master slides and the references between them are handled very neatly and are a clear example of how Aspose accurately represents the contents of documents without exposing the messy details of how they are actually stored. Aspose.Slides also exposes a large number of formats which can be saved to using the same data.

In Aspose.Cells, string tables are handled in the background and the text can simply be added to each cell in turn. Working with multiple worksheets is as simple as moving between items in a collection. All of the information about a cell (its contents, styling, format etc.) is stored and edited in one place and handling merging of cells is considerably simplified. Again, it’s also possible to save to a large number of file formats using Aspose.Cells.

Overall, Aspose provides a great abstraction to the Microsoft Office formats, whilst still maintaining a comprehensive set of features to allow you to create the full spectrum of documents that are possible in Microsoft Office. I would definitely recommend that anyone trying to automate the creation of Microsoft Office files should consider Aspose.

Amir 구매하신 고객님Israel5 등급

We evaluated many open source solutions for formats conversion and encounter with so many problems not only with implementations but also with the quality of the output files.

When I started to use Aspose Total for this task I was amazed how easy it is to use and the generated output files were just exactly as it should with no glitches, while with other solutions we had to do many configurations and workarounds to make it somehow work.

I will say that Aspose saved us a lot of developing time and I can assure the output will work and will be error free.

olivier.vermander 구매하신 고객님France5 등급

Aspose are very simple and easy-to-use components.
I do use them to export to Excel a lot of table views and it works perfectly.
I also use the Imaging to resize, crop and work with images then integrated in PDFs and that's how I easily create badges for European and French congress attendees.

I recommend these components and Aspose services. I had once an issue and posted on their forum, they answered within the day.

RichBest Companies5 등급

At Best Companies we regularly use PDF exports as a way of providing data to our clients.  Primarily being a web based business means that the majority of the information being exported is also being represented online somewhere so the simplest way of performing these exports has been to use a HTML to PDF converter, many of which are freely available.

While these tools may work for simple exports, when we came to require any sort of fine control over the PDF produced we started to run into problems using these tools.  Some of the specific problems we encountered were:
- Controlling where page breaks occur
- Finding out how many pages have been added for a piece of HTML
- Being able to edit pages once the PDF has been created
- Memory limits when generating large files

For example, when sending out paper surveys to employees we generate a large PDF containing all of the covering letters for an organisation.  These covering letters are handed to employees who are completing one of our surveys so their appearance is very important to us.  A covering letter for an employee could span many pages meaning that we wanted a high level of control over where the page breaks appeared (for example, we may not want them mid table) and we needed to be able to add unique elements for each employee after the file had been generated.  

In producing a PDF for a company, we were combining multiple covering letters into a single file.  To aid with automating the distribution process, we needed to know how many pages of the resulting file were required for each employee, as this could vary from one employee to another. The Aspose suite was a toolset we had come across for a standalone project a couple of years ago, but had not been widely adopted in the development team.  The project where it had been used was one where we wanted control over where all text appeared in a report so we knew that Aspose would offer us a level of control we couldn’t get from our existing component.

The trial version was easily imported into our project via Nuget and allowed us easily prototype a solution using Aspose.PDF.  While there are limitations on the trail version of the software, it was complete enough to validate that it would remove the limitations we had encountered with other tools and solve the technical problems we were encountering.  The online help and tutorials were a great help in getting us started working with the component and the interface was intuitive and easy to use.

We found that Aspose.PDF allowed us to generate PDFs by writing to the disk as the file is modified or perform modifications in memory, which helped us resolve memory issues we had encountered previously.  As the file is generated we were able to use the real time page count to track how many pages were required for each letter, helping us co-ordinate distribution of the file later.

The document level objects which can be added to a document (Section, Header, Text etc) gave us the control we needed to control page breaks and position additional items in the covering letter.

All in all, highly recommended. We’ll certainly be looking what else there is in the suite which we can leverage in future.