Using System.Windows namespace PdfViewerDemo
If ReferencePath is set, then PDF Viewer control extracts the PDFium binary inside that specified folder and consume the PDFium rendering engine. Update the path of this folder to the ReferencePath property of PDF Viewer control, like shown in the following code sample. Create a folder where your application can access, create & read files. In that situation, you need to add the following steps to consume the PDFium rendering engine. If there is any access restriction applied to the application output folder, then the Syncfusion PDF Viewer control cannot able to extract and consume the PDFium engine as mentioned above. How to run PDFium in a restricted access environment PDFium rendering is not supported in Windows XP operating system. Extracts the PDFium binary (PDFium.dll) into the subfolder (圆4 or x86) and consumes it to render PDF files. 
Next, it creates another subfolder named “圆4” or “x86” based on the machine architecture. Syncfusion PDF Viewer control detects the architecture of the running machine automatically. On running your WPF application, Syncfusion PDF Viewer control generates a folder named PDFium in the application output path folder (for example: bin/release or bin/debug) at runtime. How PDFium works with Syncfusion’s PDF Viewer 
It is the recommended PDF rendering engine.įrom v16.3.0.x onwards, this PDFium rendering engine is the default rendering engine of Syncfusion WPF PDF Viewer.įrom v20.1.0.x onwards, Pdfium is upgraded to the new version which was built with the branch chromium/4880. It provides accurate and robust PDF rendering. PDFium is used in Google Chrome for rendering PDF files.
SfPdf (Syncfusion’s Own PDF rendering engine). PDFium (Google Chrome’s PDF rendering engine). Syncfusion WPF PDF Viewer renders the PDF pages through 2 different rendering engines.
0 kommentar(er)
