Difference between "Evaluation Version" and "Full Version" of Aspose.Words for .NET

Hi Team,

My project team is planning to go with Aspose.Words package for solution to replace Interop library. Basically, we assemble document’s through .NET service and we already build a solution for it using Interop. Performance wise the interop library is very slow and moreover we shouldn’t use it in server machines as per Microsoft guidance. So, we are planning to replace Interop library to Aspose.Words.

I already raised a separate topic to check our use cases are feasible using Aspose.Words and we get it clarified from your team and this one is to check on few queries regarding “Evaluation Version” and “Full Version” of Aspose.Words. It would be helpful to purchase the product sooner if you answer those queries. Our development environment already have “Evaluation Version” of Aspose.Words.

The following are the queries.

  1. What’s the main difference between “Evaluation Version” and “Full Version” of Aspose.Words ? We are planning to do some POC’s in development environment using “Evaluation Version”. Is there any limitations in “Evaluation Version” apart from water mark, like page limits or functionality wise limits ?
  2. If differences are there between “Evaluation Version” and “Full Version” of Aspose.Words then, is there any documentation available in web to get a clear understanding between both the versions before we start the POC ?
  3. For doing our POC’s, can we get free real copy for non-production environment ? means “Full Version” of Aspose.Words.
  4. Is there any page limitation in “Full Version” of Aspose.Words ? We usually generate more than 700 pages of document.

Thank You,

Regards,
P.Shanmugam.

@Shan99

Please note that in evaluation mode there are some limitations applied. E.g Aspose.Words injects an evaluation watermark at the top of the document. The document’s content are truncated after a certain number of paragraphs during import or export.

To avoid this you can request a free 30-day trial license which removes these evaluation restrictions.

Please read the documentation of Aspose.Words for .NET from here:

There is no such limitation while using Aspose.Words.

Thank You Tahir for clarifying the queries and for the quick response.