diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/Instantiate-pdfviewer-dynamically.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/Instantiate-pdfviewer-dynamically.md index df71e2aac3..16ad9a2ba5 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/Instantiate-pdfviewer-dynamically.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/Instantiate-pdfviewer-dynamically.md @@ -9,11 +9,11 @@ documentation: ug # Dynamically instantiate the ASP.NET Core PDF Viewer -The Syncfusion® ASP.NET Core PDF Viewer can be instantiated at runtime rather than during the initial page load. This dynamic approach is useful when the document to be displayed depends on user interaction or must be retrieved from a secure backend service. +The Syncfusion® ASP.NET Core PDF Viewer can be instantiated at runtime rather than during the initial page load. This dynamic approach is useful when the document to be displayed depends on user interaction or must be retrieved from a secure back end service. Follow these steps to instantiate the viewer component programmatically: -1. **Verify Prerequisites:** Ensure your application references the required Syncfusion EJ2 script and style assets. The backend PDF Viewer service must be correctly configured in your ASP.NET Core application. +1. **Verify Prerequisites:** Verify that your application references the required Syncfusion EJ2 script and style assets, and that the back end PDF Viewer service is correctly configured in your ASP.NET Core application. 2. **Setup Container:** Add a target container element and a trigger (such as a button) to the Razor view. 3. **Initialize Component:** To create the viewer instance, configure the [`serviceUrl`](https://help.syncfusion.com/cr/aspnetcore-js2/Syncfusion.EJ2.PdfViewer.PdfViewer.html#Syncfusion_EJ2_PdfViewer_PdfViewer_ServiceUrl) and [`documentPath`](https://help.syncfusion.com/cr/aspnetcore-js2/Syncfusion.EJ2.PdfViewer.PdfViewer.html#Syncfusion_EJ2_PdfViewer_PdfViewer_DocumentPath), and then mount it using the `appendTo` method. @@ -22,12 +22,12 @@ The following example demonstrates how to load the viewer dynamically after an A ```html
- +
``` -## Sample: Custom context menu output +## Sample: Custom context menu The following complete sample demonstrates a customized context menu with action handlers for all menu items: diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/custom-font-signature-field.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/custom-font-signature-field.md index 25a556e2f0..bebf38acc4 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/custom-font-signature-field.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/custom-font-signature-field.md @@ -17,7 +17,7 @@ The PDF Viewer supports changing fonts for Signature and Initial fields using th **Step 1:** Follow the [Getting Started guide](https://help.syncfusion.com/document-processing/pdf/pdf-viewer/asp-net-core/getting-started) to set up a basic PDF Viewer instance. -**Step 2:** Define the signature and initial field settings in your application: +**Step 2:** Define the signature and initial field settings in your application and call the function (for example, on a button click or in the `documentLoaded` event) so the font arrays are applied to the viewer: {% tabs %} {% highlight html tabtitle="Standalone" %} @@ -51,7 +51,7 @@ The PDF Viewer supports changing fonts for Signature and Initial fields using th {% endhighlight %} {% endtabs %} -### Initial field property +### typeInitialFonts property Use the following code to apply custom fonts to the Initial field. diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/custom-fonts.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/custom-fonts.md index dcee0aa65c..cfb77994e0 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/custom-fonts.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/custom-fonts.md @@ -8,7 +8,7 @@ documentation: ug domainurl: ##DomainURL## --- -# Add custom fonts to PDF forms in ASP.NET Core PDF Viewer +# Add custom fonts in ASP.NET Core PDF Viewer The Syncfusion ASP.NET Core PDF Viewer supports loading, editing, and saving custom fonts in interactive form fields such as [TextBox](../forms/manage-form-fields/create-form-fields#textbox), [ListBox](../forms/manage-form-fields/create-form-fields#listbox), and [DropDown](../forms/manage-form-fields/create-form-fields#dropdown). Use the `customFonts` property to ensure consistent text rendering even when specific fonts are not installed on the user's system. @@ -31,7 +31,7 @@ The custom font workflow in the PDF Viewer involves these key steps: ### Step 1: Add TTF font files -Place the TTF font files in the resource path used by the PDF Viewer. Fonts can be referenced in two ways: +Place the TTF font files in the resource path used by the PDF Viewer (for example, the `wwwroot` folder in a typical ASP.NET Core project). Fonts can be referenced in two ways: * **Relative Path:** (for example: `calibri.ttf` or `fallback-fonts/calibri.ttf`) * **Absolute URL:** Host fonts on a secure server and reference them using a fully qualified URL. Ensure that the hosting server has **CORS** enabled. diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/customize-text-search-color.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/customize-text-search-color.md index 1c33d81710..a84dc95604 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/customize-text-search-color.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/customize-text-search-color.md @@ -34,7 +34,7 @@ The following example demonstrates how to configure these colors in both Standal diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/disable-tile-rendering.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/disable-tile-rendering.md index 11ee3fcc23..dcba654470 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/disable-tile-rendering.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/disable-tile-rendering.md @@ -11,7 +11,7 @@ documentation: ug Tile rendering is a performance-optimization feature used to display large PDF documents efficiently. In some scenarios, such as when viewing smaller documents or troubleshooting rendering artifacts, disabling this feature will help. -Use the **enableTileRendering** property within the `tileRenderingSettings` object to toggle this behavior. By default, tile rendering is enabled. +Use the **EnableTileRendering** property within the `tileRenderingSettings` object to toggle this behavior. By default, tile rendering is enabled. N> Disabling tile rendering can improve initial performance for small documents but may result in slower rendering and increased memory usage for larger PDF files. diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/enable-resize.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/enable-resize.md index 4bf810b11d..a04ab98922 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/enable-resize.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/enable-resize.md @@ -1,7 +1,7 @@ --- layout: post -title: Enable resize in ASP.NET Core PDF Viewer control | Syncfusion -description: Learn here all about Enable resize in Syncfusion ASP.NET Core PDF Viewer control of Syncfusion Essential JS 2 and more. +title: Resize Text Markup Annotations in Syncfusion ASP.NET Core PDF Viewer +description: Learn here all about resizing text markup annotations in Syncfusion ASP.NET Core PDF Viewer control of Syncfusion Essential JS 2 and more. platform: document-processing control: PDF Viewer documentation: ug @@ -9,13 +9,13 @@ documentation: ug # Resize text markup annotations in ASP.NET Core PDF Viewer -The PDF Viewer has the option to display resizers for text markup annotations using the **enableTextMarkupResizer** property. This feature allows users to adjust the dimensions of the markup after it has been added to the document. +The PDF Viewer has the option to display resizer for text markup annotations using the **enableTextMarkupResizer** property. This feature allows users to adjust the dimensions of the markup after it has been added to the document. The default value for this property is `false`. ## Enable text markup resizer -Set the **EnableTextMarkupResizer** property to `true` in the Razor view to display resizer handles on text markup annotations: +Set the **enableTextMarkupResizer** property to `true` in the Razor view to display resizer handles on text markup annotations: {% tabs %} {% highlight cshtml tabtitle="Standalone" %} diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/enable-text-selection.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/enable-text-selection.md index 7c14c0ceb5..0d854a7d77 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/enable-text-selection.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/enable-text-selection.md @@ -87,6 +87,6 @@ Dynamically enable or disable text selection using buttons or other UI triggers. Text selection is enabled by default. When disabled, users cannot select or copy text from the PDF, which helps protect document content in security-sensitive scenarios. -N> When `enableTextSelection` is set to `false`, all text selection functionality, including keyboard shortcuts and mouse interactions, is disabled. +N> When `enableTextSelection` is set to `false` (whether at initialization or at runtime), all text selection functionality, including keyboard shortcuts and mouse interactions, is disabled. [View sample in GitHub](https://github.com/SyncfusionExamples/asp-core-pdf-viewer-examples/tree/master/How%20to) diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/export-as-image-standalone.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/export-as-image-standalone.md index ca00d639fc..8a0e7eb703 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/export-as-image-standalone.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/export-as-image-standalone.md @@ -80,8 +80,9 @@ To export multiple pages within a range, use the **exportAsImages()** method. Th - ``` ### Conclusion diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/identify-added-annotation-mode.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/identify-added-annotation-mode.md index e13816ceb3..c1ddd2d1c5 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/identify-added-annotation-mode.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/identify-added-annotation-mode.md @@ -1,7 +1,7 @@ --- layout: post title: Identify annotation mode in ASP.NET Core PDF Viewer | Syncfusion -description: Learn here all about Identify added annotation mode in Syncfusion ASP.NET Core PDF Viewer control of Syncfusion Essential JS 2 and more. +description: Learn how to identify the current annotation addition mode in the Syncfusion ASP.NET Core PDF Viewer and manage annotation workflows efficiently. platform: document-processing control: PDF Viewer documentation: ug diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/import-export-annotation.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/import-export-annotation.md index efd06c8dd1..71bf43bc5d 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/import-export-annotation.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/import-export-annotation.md @@ -39,7 +39,7 @@ Follow these steps to implement annotation import and export functionality: - diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/local-resources.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/local-resources.md index 942a709529..b04e007970 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/local-resources.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/local-resources.md @@ -11,7 +11,7 @@ documentation: ug ## Configuring PDF Viewer with local styles and scripts -For offline deployment or when CDN access is restricted, you can use local resources required for PDF Viewer. To load the PDF Viewer with local resources, follow these steps: +For offline deployment or when CDN access is restricted, you can use local resources for the PDF Viewer. To load the PDF Viewer with local resources, follow these steps: **Step 1:** Place the `ej2.min.js` script and the required theme CSS files in the `wwwroot` folder of the ASP.NET Core application. diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/open-bookmark.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/open-bookmark.md index 8b61ec23b4..6712e63415 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/open-bookmark.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/open-bookmark.md @@ -1,6 +1,6 @@ --- layout: post -title: Open or close the bookmark pane in ASP.NET Core PDF Viewer | Syncfusion +title: Open or close the bookmark pane in Core PDF Viewer | Syncfusion description: Learn how to open or close the bookmark pane programmatically in the Syncfusion ASP.NET Core PDF Viewer by calling the bookmarkViewModule APIs. platform: document-processing control: PDF Viewer @@ -26,14 +26,14 @@ Follow these steps to implement bookmark pane toggling: + resourceUrl="https://cdn.syncfusion.com/ej2/31.1.17/dist/ej2-pdfviewer-lib"> @@ -53,7 +53,7 @@ Follow these steps to implement bookmark pane toggling: @@ -80,7 +80,7 @@ To hide the bookmark pane, call the `closeBookmarkPane()` method. Use the follow {% endhighlight %} @@ -99,7 +99,7 @@ To hide the bookmark pane, call the `closeBookmarkPane()` method. Use the follow diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/pagerenderstarted-pagerendercompleted.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/pagerenderstarted-pagerendercompleted.md index fd9bdeaf3a..61094cf407 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/pagerenderstarted-pagerendercompleted.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/pagerenderstarted-pagerendercompleted.md @@ -1,6 +1,6 @@ --- layout: post -title: Handle pageRenderInitiate and pageRenderComplete events in ASP.NET Core PDF Viewer | Syncfusion +title: Handle Page Render Events in Syncfusion ASP.NET Core PDF Viewer description: Discover how to use the pageRenderInitiate and pageRenderComplete events in the Syncfusion ASP.NET Core PDF Viewer to monitor page rendering stages. platform: document-processing control: PDF Viewer @@ -9,11 +9,11 @@ documentation: ug # Page rendering events in ASP.NET Core PDF Viewer -The Syncfusion® ASP.NET Core PDF Viewer provides the `pageRenderInitiate` and `pageRenderComplete` events to monitor and respond to each stage of the page rendering lifecycle. These events are essential for tracking progress, managing specialized UI overlays, or deferring computational tasks until a page is fully visible. +The Syncfusion® ASP.NET Core PDF Viewer provides the `pageRenderInitiate` and `pageRenderComplete` events to monitor and respond to each stage of the page rendering life cycle. These events are essential for tracking progress, managing specialized UI overlays, or deferring computational tasks until a page is fully visible. ## pageRenderInitiate -The `pageRenderInitiate` event fires correctly before a page enters the rendering process. This is the ideal stage to initialize timers, allocate temporary resources, or log analytical data. The event arguments provide the specific page index and source details. +The `pageRenderInitiate` event fires before a page enters the rendering process. This is the ideal stage to initialize timers, allocate temporary resources, or log analytical data. The event arguments provide the specific page index and source details. ## pageRenderComplete @@ -83,4 +83,4 @@ The following example demonstrates how to subscribe to these events in both stan {% endhighlight %} {% endtabs %} -By leveraging these rendering events, developers can maintain granular control over the viewer's lifecycle and provide a more interactive documentation experience. +By leveraging these rendering events, developers can maintain granular control over the viewer's life cycle and provide a more interactive documentation experience. diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/resolve-Unable-to-find-an-entry-point-error.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/resolve-Unable-to-find-an-entry-point-error.md index d9f362694a..04a191c9de 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/resolve-Unable-to-find-an-entry-point-error.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/resolve-Unable-to-find-an-entry-point-error.md @@ -1,17 +1,17 @@ --- layout: post -title: Resolve “Unable to find an entry point named FPDFText_GetCharAngle” error in ASP.NET Core PDF Viewer | Syncfusion -description: Resolve the “Unable to find an entry point named FPDFText_GetCharAngle” error in the Syncfusion ASP.NET Core PDF Viewer by updating the PDFium assemblies and republishing the service. +title: Fix FPDFText_GetCharAngle Entry Point Error | Syncfusion +description: Fix the “Unable to find an entry point named FPDFText_GetCharAngle” error in Syncfusion ASP.NET Core PDF Viewer by updating PDFium files and redeploying. control: PDF Viewer platform: document-processing documentation: ug --- -# Resolve "Unable to find an entry point named FPDFText_GetCharAngle" error +# Handle FPDFText_GetCharAngle Entry Point Resolution Issues Effective with Essential Studio® version 21.1.0.35 (2023 Volume 1), the Syncfusion® PDF Viewer includes an updated PDFium engine to enhance text search, selection, and overall rendering performance. If an application continues to reference legacy native PDFium binaries after upgrading NuGet packages, it may trigger the exception: **"Unable to find an entry point named FPDFText_GetCharAngle"**. -This error typically results in the client displaying a **"Web-Service is not listening"** status. This can be confirmed by inspecting the **Network** tab in the browser developer tools, where the service response will indicate a failure due to missing or mismatched PDFium assemblies. +This error typically causes the client to display a **"Web-Service is not listening"** status. This can be confirmed by inspecting the **Network** tab in the browser developer tools, where the service response will indicate a failure due to missing or mismatched PDFium assemblies. ## Troubleshooting steps diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/resolve-pdfium-issue.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/resolve-pdfium-issue.md index 99575617c5..36b0702b7f 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/resolve-pdfium-issue.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/resolve-pdfium-issue.md @@ -1,16 +1,16 @@ --- layout: post -title: Resolve PDFium initialization error in ASP.NET Core PDF Viewer | Syncfusion -description: Fix the “The type initializer for Syncfusion.EJ2.PdfViewer.PdfiumNative threw an exception” error in the Syncfusion ASP.NET Core PDF Viewer by copying the PDFium binaries and configuring ReferencePath. +title: Fix PDFium Initialization Error in Core PDF Viewer | Syncfusion +description: Fix the “Syncfusion.EJ2.PdfViewer.PdfiumNative” initialization error in ASP.NET Core PDF Viewer by copying PDFium binaries and setting ReferencePath. platform: document-processing control: PDF Viewer documentation: ug --- -# Resolve the Pdfium issue +# Address PDFium Dependency Issues -The error “The type initializer for `Syncfusion.EJ2.PdfViewer.PdfiumNative` threw an exception” occurs when the PDF Viewer cannot unpack the required PDFium native binaries because write access is blocked or the assemblies are missing. The viewer extracts `pdfium.dll` at runtime based on the current operating system, so ensure the application can write to the target folder or manually include the binaries by copying the x64 and x86 folders into the project. +The error “The type initializer for `Syncfusion.EJ2.PdfViewer.PdfiumNative` threw an exception” occurs when the PDF Viewer cannot unpack the required PDFium native binaries because write access is blocked or the assemblies are missing. The viewer extracts `pdfium.dll` at runtime based on the current operating system. Ensure the application can write to the target folder, or manually include the binaries by copying the x64 and x86 folders into the project. Pdfium DLL package: [pdfium.dll](https://www.syncfusion.com/downloads/support/directtrac/general/ze/Pdfium1334927507.zip) @@ -29,7 +29,7 @@ pdfRenderer.ReferencePath = @"C:/Pdfium/"; ## Steps to refer the PDFium.dll 1. Extract the downloaded Pdfium archive and copy the entire folder into the application’s root directory (parallel to the `Controllers` folder) so both `x64` and `x86` subfolders are available. -2. In Solution Explorer, select `pdfium.dll` within the `x64` and `x86` folders, open the Properties window, and set **Copy to Output Directory** to **Copy always**. This ensures the assemblies are packaged during publish. +2. In Solution Explorer, select all files within the `x64` and `x86` folders (including `pdfium.dll`), open the Properties window, and set **Copy to Output Directory** to **Copy always**. This ensures every native binary in those folders is packaged during publish. ![Pdfium.dll settings](../images/pdfium_dll_settings.png) 3. Update the `Load` method in `PDFViewerController.cs` to point to the parent Pdfium folder. The reference should target the folder that contains the architecture folders. N> `PdfRenderer.ReferencePath = _hostingEnvironment.ContentRootPath + "\\Pdfium\\";` diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/retry-timeout.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/retry-timeout.md index 0f9a0bdd5a..db697ea035 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/retry-timeout.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/retry-timeout.md @@ -7,14 +7,14 @@ control: PDF Viewer documentation: ug --- -# Configure retry timeout and retry count +# Adjust Retry Attempts and Timeout Duration The Syncfusion® ASP.NET Core PDF Viewer provides the [`retryTimeout`](https://help.syncfusion.com/cr/aspnetcore-js2/syncfusion.ej2.pdfviewer.pdfviewer.html#Syncfusion_EJ2_PdfViewer_PdfViewer_RetryTimeout) and [`retryCount`](https://help.syncfusion.com/cr/aspnetcore-js2/syncfusion.ej2.pdfviewer.pdfviewer.html#Syncfusion_EJ2_PdfViewer_PdfViewer_RetryCount) properties to manage failed AJAX requests automatically. Configuring these settings improves application resilience by handling transient network fluctuations or temporary service unavailability without disrupting the user experience. -* **retryTimeout:** Defines the duration (in seconds) the viewer waits for a response before aborting and retrying the request. The default value is `0`, which disables the retry delay. +* **retryTimeout:** Defines the duration (in seconds) the viewer waits for a response before aborting and retrying the request. The default value is `0`, which means retries occur with no delay. * **retryCount:** Specifies the maximum number of retry attempts the viewer should perform before reporting a definitive error. The default value is `0`, meaning no retries are attempted. -Assigning positive values to both properties ensures the viewer proactively manages connection issues. +Assigning positive values to both properties ensures the viewer pro actively manages connection issues. The following example demonstrates how to configure these properties in a server-backed PDF Viewer setup. @@ -41,6 +41,6 @@ In this configuration, if the service does not respond within 10 seconds, the vi ## Monitoring failures -To provide a better user experience, monitor the [`ajaxRequestFailed`](https://help.syncfusion.com/cr/aspnetcore-js2/syncfusion.ej2.pdfviewer.pdfviewer.html#Syncfusion_EJ2_PdfViewer_PdfViewer_AjaxRequestFailed) event. This helps in logging failures or displaying custom notifications once all retry attempts have finished. +To provide a better user experience, you can monitor the [`ajaxRequestFailed`](https://help.syncfusion.com/cr/aspnetcore-js2/syncfusion.ej2.pdfviewer.pdfviewer.html#Syncfusion_EJ2_PdfViewer_PdfViewer_AjaxRequestFailed) event. This helps in logging failures or displaying custom notifications once all retry attempts have finished. [View sample in GitHub](https://github.com/SyncfusionExamples/asp-core-pdf-viewer-examples/tree/master/How%20to/RetryTimeout) diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/save-original-document-at-the-server-side.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/save-original-document-at-the-server-side.md index f212cee74b..e74f65cd0a 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/save-original-document-at-the-server-side.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/save-original-document-at-the-server-side.md @@ -1,19 +1,19 @@ --- layout: post -title: Save the original document on the server in ASP.NET Core PDF Viewer | Syncfusion +title: Save Original Documents on Server in Core PDF Viewer | Syncfusion description: Learn how to save the original PDF document on the server by calling a custom download action in the Syncfusion ASP.NET Core PDF Viewer. platform: document-processing control: PDF Viewer documentation: ug --- -# Save original document at the server side +# Manage Original Document Storage on the Server The Syncfusion® PDF Viewer can persist the original PDF file on the server by redirecting the download action to a custom controller method. This approach is useful for audit trails, archival policies, or downstream processing that requires access to the unmodified document after the user views it. Follow these steps to enable server-side persistence: -**Step 1:** Create a PDF Viewer project by following the [ASP.NET Core getting started guide](https://help.syncfusion.com/document-processing/pdf/pdf-viewer/asp-net-core/getting-started/) to configure the necessary scripts, Razor markup, and controller endpoints. +**Step 1:** Create a PDF Viewer project by following the [ASP.NET Core getting started guide](https://help.syncfusion.com/document-processing/pdf/pdf-viewer/asp-net-core/getting-started) to configure the necessary scripts, Razor markup, and controller endpoints. **Step 2:** Add a button to the user interface that overrides the download action before invoking the viewer's `download` method. The script below targets the `serverActionSettings.download` endpoint, triggers the download, and then restores the default action. @@ -22,7 +22,7 @@ Follow these steps to enable server-side persistence: @@ -75,7 +75,7 @@ The following example demonstrates how to subscribe to these events in both stan console.log('Signature selected:', args); } function signatureUnselect(args) { - console.log('Signature selected:', args); + console.log('Signature unselected:', args); }; diff --git a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/webservice-not-listening.md b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/webservice-not-listening.md index eecbf0ccdb..78ce97f388 100644 --- a/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/webservice-not-listening.md +++ b/Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/webservice-not-listening.md @@ -1,17 +1,17 @@ --- layout: post -title: Resolve “Web service is not listening” error in ASP.NET Core PDF Viewer | Syncfusion -description: Troubleshoot the “Web service is not listening” error in the Syncfusion ASP.NET Core PDF Viewer by validating network requests, cache configuration, and server availability. +title: Fix Web Service Not Listening Error in Core PDF Viewer | Syncfusion +description: Troubleshoot the “Web service is not listening” error in Syncfusion ASP.NET Core PDF Viewer by checking requests, cache settings, and server status. platform: document-processing control: PDF Viewer documentation: ug --- -# Resolve “Web service is not listening” error +# Fix Web Service Connectivity Issues in PDF Viewer ![Browser showing the Web service is not listening error](../images/webservice.png) -The Syncfusion® ASP.NET Core PDF Viewer displays the **Web service is not listening** message when the component cannot establish a connection with the backend service or the service encounters an unhandled exception. Follow these diagnostic steps to identify and resolve the issue. +The Syncfusion® ASP.NET Core PDF Viewer displays the **Web service is not listening** message when the component cannot establish a connection with the back end service or the service encounters an unhandled exception. Follow these diagnostic steps to identify and resolve the issue. ## Diagnose the service response @@ -59,7 +59,7 @@ The `Document pointer does not exist in the cache` exception indicates a mismatc To resolve this issue: 1. **Clear the Cache:** Manually clear the contents of the cache directory specified in the PDF Viewer settings to remove corrupted or stale data. -2. **Reload the Document:** Programmatically invoke the `Load()` method via the controller to re-initialize the document session. +2. **Reload the Document:** Programmatically invoke the `Load()` method on the client viewer instance to re-initialize the document session. 3. **App Restart:** Restart the application pool or service to refresh component states and clear memory-resident metadata. ## Internal server error