Opiniones sobre Aspose.Total for .NET

Puntuación de revisión media: 5 (26)

5 de 5 estrellas

5 estrella
4 estrella
3 estrella
2 estrella
1 estrella

Comentario positivo más reciente

Nombre retenido Francia5 estrella

Très belle suite de composants,, une référence de poids sur son domaine.

Comentario crítico más reciente

Hay no hay críticas negativas de este producto.
Nombre retenido cliente verificadoFrancia5 estrella

Très belle suite de composants,, une référence de poids sur son domaine.

João Pereira cliente verificadoPortugal5 estrella
AnónimoRumania5 estrella

Aspose components are well documented, very easy to integrate in the target applications. Also, they deliver expected results, without major difficulties in use. All importing and exporting of excel files are based on Aspose.Cells. Totalsoft built, using this component, a functionally which allows consultants to implement flexible exports to excel files. It has support for formula configuration and validation. After export to excel is finalized, a set of formulas are applied to get exactly the information need in the requested format. Different character sets are supported, including Chinese and Cyrillic. Also, excel files import and transformation for different processing needs are based on the Aspose.Cells component.

Programmers found Aspose.Cells very easy to use and easy to integrate component. Performance in working with a large volume of data was very good.

Chokchai LertratanakulTailandia5 estrella

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 mehtaIndia5 estrella

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.

Nombre retenido cliente verificadoEslovenia5 estrella
Nombre retenido cliente verificadoEE.UU.5 estrella
mamtaaIL, USA5 estrella

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 estrella

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 estrella

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.