Skip to main content
May 16, 2017
Question

Adobe PDF Reader COM-Components licensing

  • May 16, 2017
  • 1 reply
  • 4745 views

Hello there,

i would like to use the adobe pdf reader com components in my application to show pdf files, which is selled to our customers.

So I read a lot about licensing in this forum but my answer is still not clear.

So I explain my steps:

1. I added a Windows Forms UserControl to my Application, then added Adobe PDF Reader Com-Components to the UserControl. (VS 2017)

2. When i perform step 1 , two libraries are automatically added to my project, AcroPDFLib and AxAcroPDFLib.

When I Compile my project now, these two dll's are copied to my Debug/Release folder.

To Run the Appliaction these Two libraries are needed.

I dont't want to deliver Adobe PDF Reader at all, i just want to deliver these two dll's do my customers. If they have Adobe reader installed, fine it will work and pdf files are shown with Adobe Pdf reader, if not installed, a webbrowser control will just offer to download .Pdf files instead of showing them.

Is there any need in this case to license it? The two libraries are useless in case Adobe Reader is not installed, i know, but for my application it will not cause a problem.

This topic has been closed for replies.

1 reply

Legend
May 16, 2017

You MUST NOT distribute these files. If you apply for a Reader distribution license you can get certain limited rights to distribute the installer only, never loose components. You must adapt you app to work with these files as they are installed.

May 16, 2017

Okay I read that Interop.AcroPDFLib and AxInterop.AcroPDFLib are just auto-generated wrapper files, when adding Adobe PDF Reader from toolbox to designer (visual studio). That means they aren't loose components or? And if no, then i am allowed to deliver them without any license or?

I Found a nice link: why do we need AxInterop.AcroPDFLib.dll to create an adobe reader instance from a .net application