Where is AVExtensionMgrRegisterNotification, or AVAppRegisterNotification?

[Guest]

Where is AVExtensionMgrRegisterNotification, or AVAppRegisterNotification ?

I am working on the first Adobe Reader plugin, and wondering where the APIs such as AVExtensionMgrRegisterNotification, or AVAppRegisterNotification are from?

On Windows, I looked into all the Adobe Reader DLLs, such as AcroRd32.dll, but cannot find any exported functions like above.

So how can the plugins access these APIs, if they are not exported in any DLLs?

Thanks

[Test Screen Name]

The plugin API does not use DLL entry points. All the linkage takes place when Acrobat loads the plugin. You should start by compiling sample plugins and attempting loading them in Acrobat (NOT ACROBAT READER) until this works and things start to make sense. Only then start to adapt for your needs.

[Guest]

Thanks so much for the quick reply, but unfortunately that does not answer my question: I am wondering which Adobe DLL provide the AVAppRegisterNotification API (or similarly, AVExtensionMgrRegisterNotification)

Btw, why did you say Acrobat, but *not* Acrobat Reader?

Thanks a lot for your kind help

[Guest]

I looked at all the DLLs under "Reader" directory, and cannot find any DLL exported AVAppRegisterNotification(), thus my question.

So I dont understand why the plugin can call this function.

I hope my question is more clear now.

Thanks

[Test Screen Name]

I didn't answer because the services are not provided by a DLL. Your question suggests you are trying to just write new code using the APIs: do not do this. I said Acrobat not Reader because that is what you need to do. Samples can only be used with Acrobat. You will need to license Acrobat and use Acrobat initially, before finally applying for your license to write Reader plugins. 

[Test Screen Name · Accepted solution]

Yes, your question is clear. But the answer does not change. (1) you need Acrobat not Reader (2) entry points are not in DLLs.

Technically, linkages are done using HFTs, function tables that are made available during the handshake call in your PluginMain function. All the linkages from from PluginMain in your C code.

It is clear you don't want to license Acrobat, and don't want to start with the samples. Good luck with that.

[Guest]

Yes, I am trying to do some private experiments with Reader, and for what I want, having to buy a license is really overkill.

I see how the HFTs work in the architecture now, thanks again for your kind helps.

[Test Screen Name]

You haven't said but I suspect you may be making the other Big Mistake so popular with plug-in beginners: you are trying to avoid writing in C or C++. No, you cannot. Furthermore, to avoid complex issues, use ONLY the version of Visual Studio documented in the SDK you are using.

[Guest]

No, C/C++ is my favorite language, i dont want to avoid them 😉

[Test Screen Name]

Not overkill, but mandatory. You cannot load plug-ins into Reader unless you get a Reader Plug-in license. They just will not load unless signed with an Adobe-supplied key. Reader plug-in licenses are only granted in limited situations: they are not allowed to add functionality found only in Acrobat. Prices are variable: the most expensive are plug-ins that implement security. These "DRM plug-ins" typically cost $50,000 per year plus royalty payments ( Developing digital rights management (DRM) plug-ins | Adobe Developer Connection )

So even the simplest experiments will need Acrobat. Bear in mind you can subscribe. Notice cancellation terms: the cheaper subscriptions are for a year commitment.

[Test Screen Name]

That's good. We hear from a lot of people whose problems flow from trying to learn C++ for the first time at the same time as trying to write their first plug-in. As we know, a lot can go wrong...