Unfortunately AcroPDF.dll throws error when trying to install it using regsvr32.exe.
UPDATE (July 27 2015): In the latest versions of Adobe Reader they use AcroPDF.dll and moved it into \Program Files\Common Files\Adobe\Acrobat\ActiveX\ as I've checked with Adobe Reader 11. I assume that for Adobe Reader control you should use PDF.ocx from C:\Program Files\Adobe\Acrobat \Reader\ActiveX folder. See this post for the list of tools and this post for sample XML manifest to use Flash plugin and this step by step guide. Have you considered the use of " Registration free" scenario? It allows to use COM/ActiveX components in your application without registering the ActiveX globally and allows to load the isolated COM/ActiveX control for your application only based on the interfaces defined in the XML manifest included along with your application. The primary priority is to understand the solution for DC as this represents the new paradigm for Adobe Acrobat/Reader.
I can't seem to find any references online for how to enable/disable browser integration from a developer standpoint so our application can continue to the use the ActiveX Control and not have the COM errors show up, forcing the user to change this manually. We want to be able to turn it on and then reset it to the previous setting when our application ends (so our application doesn't force the user to keep the setting just because our application needs it) which is what we do today for 7-10.
So, the question remains, what is the expected programmatic equivalent either for the manual process in XI or DC today or the equivalent to what worked in 7-10 by setting the registry setting bBrowserIntegration accordingly.
When testing Adobe Reader DC, if we don't complete the steps to enable the Display PDF in Browser for a new customer installation, then our application will throw a COM error and then if we enable the setting following the instructions in the link above, everything works as expected with our application, it renders PDFs using the Adobe ActiveX Control, which is similar to what we expect to see in older versions (7-10) when the registry setting was not set (see my old post and my own solution back then How to diagnose cause, fix, or work around Adobe ActiveX / COM related error 0x80004005 progmatically?). It does appear that the Adobe ActiveX Control still works just fine with XI and DC as long as Display PDF in Browser is enabled, as it always has.įor versions XI (11) and DC, there are two published links that clearly show how to achieve this manually: XI (11): However there is no longer a bBrowserIntegration key just as the documentation indicates, it is deprecated. The old registry path still exists in the new versions, i.e.: HKEY_CURRENT_USER\Software\Adobe\(Product Name)\(Version)\Originals The link above also indicates that this bBrowserIntegration registry key is deprecated in XI (11). Our application has been using the programmatically setting of this registry value when our customers have versions 7-10 of Adobe Reader or Adobe Acrobat. Or programmatically by setting the registry settings directly HKEY_CURRENT_USER\Software\Adobe\(Product Name)\(Version)\Originals You could do this manually from the GUI using Preferences > Internet > Display PDFs in browser For versions 7-10 of both Adobe Acrobat and Adobe Reader, to use this control you were required to turn on the "Display PDF In Browser" setting. NET C# application that makes use of the Adobe ActiveX Controls. Microsoft does not guarantee the accuracy of this third-party contact information.We have a. This contact information may change without notice. Please Note: Microsoft provides third-party contact information to help you find technical support. Please follow the steps from the link above to fix the issue.
Regarding the error 1935, it seems this is a general Acrobat related issue, I would like to share the link below with you:Īcrobat X installation freezing windows 7
NET Framework can help in this situation. NETįrameworks, removing orphaned registry keys that can remain, then reinstalling the. NET Framework than the one being installed. In some cases, the 1935 error results from orphaned registry keys from a different version of the. If this process is running, then you remove this adware.Ĥ. I would like to suggest you remove adware and then install Acrobat or Adobe Reader.Ģ. You may disable antispyware and antivirus software or remove adware or spyware from your computer and then install Acrobat or Adobe Reader as BrianD_22932 mentioned.Īs I known, a certain type of adware running on the system can cause 1935 errors.