Knowledgebase

Symptoms: 

The PDF-Xchange Viewer ActiveX control displays unexpected behaviour in your application.

Cause:

The DLLs that the PDF-XChange Viewer ActiveX control uses in your application are not isolated. This means that changes/conflicts may arise with other PDF-XChange applications on the systems of end users.

Resolution:

Windows requires the specification of two substitute, XML-formatted files in order to isolate the DLLs:

• Server.X.manifest, which contains information about the external COM-components that the Client.exe application will use.
• Client.exe.manifest, which contains a brief description about the Client.exe assembly and any dependency between the Client and Server architecture.

Examples of these files are included in the PDF-XChange Viewer ActiveX SDK example folder "Registration-Free COM":

• PDFXCviewAx.X.manifest file (the sample server file).
• Client.exe.manifest - (the sample client file, which is a template manifest for any client application).

Follow the steps below to isolate the DLLs:

1. Copy the files detailed above into your program folder.

2. Rename the Client.exe.manifest to <YourProgramName>.exe.manifest.

3. Open <YourProgramName>.exe.manifest, then replace name="Client" with name="<YourProgramName>" and save the changes.

4. Check that your program folder contains the following files:

• <YourProgramName>.exe
• <YourProgramName>.exe.manifest
• PDFXCviewAx.X.manifest
• PDFXCviewAx.dll
• PDFXCview.exe resource.dat

The application detailed in <YourProgramName>.exe application will then be able to load and use the Viewer control without the standard COM-integration that is usually required on a target system.