Create customized plugin in adobe

[shashi_8513]

I’m trying to create a plugin in Adobe. I’ve written the code in Visual Studio, and it compiles without any errors. I copied the DLL file to the plugins folder and renamed the DLL to an API. I also closed Adobe and reopened it with administrator rights, but I still can’t see my plugin in Adobe. When I go to Help → Generate System Report, I can see my plugin listed there, but it’s not visible within Adobe itself. Please let me know when you’re available so we can connect and take a look together.

[Kevin Stohlmeyer]

What application is the plugin being developed for?

[shashi_8513]

The plugin is being developed for Adobe Acrobat Pro 2020.

[Thom Parker]

So first, have you downloaded the Acrobat SDK? An Acrobat plug-in is written using the SDK. 

The SDK contains samples that are ready to compile and can be used as a template.

[shashi_8513]

I have compiled the basic plugin locally without any errors. After generating the DLL file, I replaced the existing one in the .api folder. However, I am not able to see any changes in Adobe

[Thom Parker]

By "basic plugin" do you mean the basic plugin from the SDK samples? 

If so, and you copied it into the Acrobat plug-ins folder, and then closed and restarted Acrobat, then it should be loaded. 

If the plug-in adds UI items, then you'll see those items. If not, you can use JavaScript to see all of the loaded plug-ins. 

Open the Acrobat Console window and execute this line of code:

app.plugIns

There are security settings in Acrobat that will prevent plug-ins from being loaded. 

Open the preferences dialog.  Check the "General" and "Security" categories. Remove all security settings. 

I'd also suggest reverting to the old Acrobat UI if you are using new 64bit UI.

And finally, in general, you have to provide specific information if you want help. We can't psychically tell what you are doing. For example, what specific UI items are added by the plug-in and where are you looking for them?  Did you follow the examples exactly. Are you following the directions in the SDK documentation for the VS settings?