We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Are Aspose.Pdf.Generator and Aspose.Pdf.Facades depricated?


Do I understand right that all the code moves from Aspose.Pdf.Generator and Aspose.Pdf.Facades to Aspose.Pdf in order to follow DOM API conception?

For example,
Aspose.Pdf.Facades.FormEditor can add a field to a form and Aspose.Pdf.Document.Form can do the same?

Which one is better to use?

What is the way to add JavaScript to an existing pdf document without Aspose.Pdf.Facades.FormEditor?


Hi Mikhail,

Thanks for your interest in our products.

You can use Aspose.Pdf.Generator namespace to generate new documents from scratch, and you can use Aspose.Pdf namespace or Aspose.Pdf.Facades namespace while working with existing PDF documents. However, all the feature of Aspose.Pdf.Kit can be found under Aspose.Pdf.Facades namespace in the merged application. You may also check the following links for details regarding migrating from old versions to Aspose.Pdf for .NET v6.x.


Moreover, some features may be available under both namespaces Aspose.Pdf and Aspose.Pdf.Facades while working with existing PDF documents. You can use whatever you want.

Please feel free to contact support in case you need any further assistance.

Thanks & Regards,

Hi Mikhail,

Thanks for contacting support.

Adding more to Rashid’s comments, since the release of Aspose.Pdf for .NET 6.0.0, a new Document Object Model was introduced which provides the capability to create PDF flies from scratch as well as it provides the facility to edit/manipulate exiting PDF documents. However Aspose.Pdf.Generator and Aspose.Pdf.Facades namespaces were introduced to provide the support for legacy products code.

Aspose.Pdf namespace is recently developed and I would recommend you to please try using it as its comparatively faster and stable as compare to Aspose.Pdf.Facades. In case you encounter any issue or you have any further query, please feel free to contact.