Foxit Developer

FAQ ​

After upgrading to 4.0, Node.js samples or projects fail to install or load the module. What should I do? ​

Use the English-region npm package @foxitsoftware/foxit-pdf-conversion-sdk-node. Replace any previous @fuxinsoft/foxit-pdf-conversion-sdk-node references in dependencies and code, reinstall, and verify the native module loads. See Release notes v4.0 · Node.js npm package name.

PDF ↔ Markdown reports a license failure or the API is unavailable. How do I fix it? ​

Confirm the license includes the required modules: PDF → Markdown needs PDF2MD; Markdown → PDF needs MD2PDF. Initialize with Library.Initialize / Library::Initialize before calling conversion APIs. See Trial and licensing.

What is the difference between standalone Conversion SDK and PDF SDK plug-in namespaces? ​

Standalone Foxit Conversion SDK C++ APIs use foxit::conversion::… (for example foxit::conversion::pdf2md). When used as a desktop/server PDF SDK plug-in, the corresponding APIs are under foxit::addon::conversion::…. Choose headers and samples for your integration path; capability details are also in Markdown and PDF.

How do I fix the xcopy exited with code 9009 error when building demos in Visual Studio? ​

When building demos in Visual Studio, if you see xcopy exited with code 9009 like this:

sh
xcopy ..\..\..\..\..\..\lib\conversionsdk\_sn.txt ..\..\..\ /y > null
xcopy ..\..\..\..\..\..\lib\conversionsdk\_key.txt ..\..\..\ /y > null
xcopy ..\..\..\..\..\..\lib\$(PlatformName)\_vc10\fpdfconversionsdk\_win32.dll..\..\..\ /y > null
xcopy ..\..\..\..\..\..\lib\$(PlatformName)\_vc10\fpdfconversionsdk\_win64.dll..\..\..\ /y > null' exited with code 9009

Please check the following:

  1. Confirm xcopy.exe exists under "%SystemRoot%\System32". If not, copy it from another machine.
  2. Confirm the system PATH includes "%SystemRoot%\System32;%SystemRoot%;". If xcopy is configured correctly but the error persists, try moving the xcopy path to the front of PATH. A misspelled entry earlier in PATH can invalidate later entries—verify carefully.

After checking, run xcopy from a command prompt. If the system recognizes it, close Visual Studio and rebuild the demo; the error should be resolved.