Building Custom PDF Tools with PDF-XChange Viewer Pro SDK

PDF-XChange Viewer Pro SDK: Troubleshooting & Best Practices

Common problems & quick fixes

• Activation/registering not applied: Ensure the license key matches the installed version/build. If you upgraded or installed a different build, reapply the key for that exact build.
• Runtime crashes or exceptions: Use DebugView to capture API/system calls; collect the log and reproduce the problem in a minimal sample.
• Incorrect rendering or corrupted output: Test with the original PDF in PDF-XChange Editor; compare object properties and fonts. Try regenerating the PDF with a known-good source to isolate input vs SDK conversion issues.
• Missing functionality after integration: Verify you installed the correct SDK variant (Viewer Pro vs other SDKs) and that required DLLs are deployed alongside your app (correct bitness: x86 vs x64).
• License/registration differences across machines: Licenses may be build-specific and limited by maintenance—confirm license entitlement and use the installer version the key was issued for.

Debugging best practices

1. Reproduce in a minimal sample: Strip your app to the smallest project that demonstrates the issue.
2. Capture diagnostic logs: Use DebugView and any SDK-provided logging; save logs and relevant PDF samples.
3. Confirm environment details: Note SDK version/build, OS and service pack, compiler/IDE and runtime (e.g., Visual Studio version, .NET runtime), and ⁄₆₄-bit.
4. Compare with official samples: Run the SDK sample apps to see if the issue appears there.
5. Isolate third-party interactions: Disable or remove other PDF toolchains and plugins (Office add-ins, antivirus PDF hooks) when reproducing.

Integration & deployment best practices

• Match bitness: Build and deploy DLLs for the same architecture as your app (x86 vs x64).
• Distribute required runtime files: Include all dependent SDK DLLs and VC++/.NET runtimes the SDK requires.
• Use correct installer for licensing: Install the SDK version corresponding to your license to avoid activation problems.
• Keep sample code handy: Use and adapt SDK samples rather than rewriting integration code from scratch.
• Error handling: Wrap SDK calls with robust exception handling and validate returned error codes/messages.

When to contact PDF‑XChange support

• Provide: SDK version and build number, OS and environment details, compiler/IDE and bitness, a minimal reproducible sample (zipped), DebugView/log output, and the problematic PDF(s).
• Send attachments zipped and do NOT post license keys publicly; email [email protected] for private files.

Security & maintenance tips

• Keep SDK and runtime components updated to the latest supported builds for bug fixes and security patches.
• Test upgrades in a staging environment to verify license compatibility and behavior before production rollout.

If you want, I can turn this into a checklist you can use when filing support tickets.