[]
You may notice references to "Document Solutions" (or GrapeCity Document) packages within your ActiveReports.NET projects. This can lead to questions about licensing and whether you can directly utilize Document Solutions APIs within your ActiveReports application. This article clarifies the relationship between ActiveReports and Document Solutions to prevent confusion and ensure you understand the licensing implications.
ActiveReports, in order to provide robust and advanced document processing features, internally utilizes components from Document Solutions. This means that certain Document Solutions assemblies are referenced and leveraged within the ActiveReports engine itself to power features like:
While ActiveReports references and uses Document Solutions assemblies internally, this does not mean that a license for ActiveReports automatically includes a license to directly utilize any of the Document Solutions APIs in your own application code.
In summary:
Users often encounter the following packages and may assume they can directly use them based on their ActiveReports license. Please note that using APIs within these namespaces directly requires a separate Document Solutions license:
If you attempt to directly use classes or methods within these namespaces without a Document Solutions license, you will encounter licensing errors and/or limitations in functionality.
You would need a separate Document Solutions license if you want to:
If you require the ability to directly utilize a Document Solutions API in your application for document manipulation tasks beyond ActiveReports reporting, you will need to obtain a separate license for the appropriate Document Solutions product.
To learn more about Document Solutions, including licensing options, pricing, and features, please visit the following resources: