1010339: Core documentation revamp

Author: BalajiLoganathanSF4826

Document-Processing/PDF/PDF-Viewer/asp-net-core/annotation/free-text-annotation.md

@@ -35,7 +35,7 @@ Free text annotations can be added to PDF documents using the built-in annotatio
 - Type your text directly into the text box
 - Use the formatting toolbar to adjust font, size, color, and alignment
 
-> **Note:** When in pan mode and free text annotation is selected, the PDF Viewer automatically switches to text select mode for smooth interaction.
+N> When in pan mode and free text annotation is selected, the PDF Viewer automatically switches to text select mode for smooth interaction.
 
 **Example: Enable free text annotation mode**
 

Document-Processing/PDF/PDF-Viewer/asp-net-core/annotation/shape-annotation.md

@@ -46,7 +46,7 @@ Shape annotations can be added to PDF documents using the built-in annotation to
 - Release to complete the shape placement
 - Use handles to resize and reposition as needed
 
-> **Note:** When in pan mode and a shape annotation tool is selected, the PDF Viewer automatically switches to text select mode for smooth interaction.
+N> When in pan mode and a shape annotation tool is selected, the PDF Viewer automatically switches to text select mode for smooth interaction.
 
 **Example: Switch to circle annotation mode**
 

Document-Processing/PDF/PDF-Viewer/asp-net-core/event.md

@@ -66,7 +66,7 @@ The following table lists all events supported by the PDF Viewer control, organi
 | [`validateFormFields`](#validateformfields) | Triggers when form field validation fails. |
 | [`zoomChange`](#zoomchange) | Triggers when the magnification value changes. |
 
-Note: For annotation and signature events, see the dedicated Annotations Events topic.
+For annotation and signature events, see the dedicated Annotations Events topic.
 
 ## bookmarkClick
 

Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/Instantiate-pdfviewer-dynamically.md

@@ -9,13 +9,15 @@ documentation: ug
 
 # Dynamically instantiate the ASP.NET Core PDF Viewer
 
-Create the Syncfusion<sup style="font-size:70%">&reg;</sup> PDF Viewer instance at runtime when a document request succeeds, instead of rendering it during the initial page load. This approach is useful when the PDF is determined after user input or must be fetched securely from a server endpoint.
+The Syncfusion<sup style="font-size:70%">&reg;</sup> 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.
 
-Follow these steps to instantiate the component dynamically:
+Follow these steps to instantiate the viewer component programmatically:
 
-- Confirm that the application references the required Syncfusion EJ2 scripts and styles and that the PDF Viewer service endpoint is available in the ASP.NET Core application.
-- Add a container element and a button (or another trigger) to the Razor view. The trigger initiates an AJAX request that retrieves the document information.
-- Inside the callback, create a new viewer instance, set its [`serviceUrl`](https://help.syncfusion.com/cr/aspnetcore-js2/Syncfusion.EJ2.PdfViewer.PdfViewer.html#Syncfusion_EJ2_PdfViewer_PdfViewer_serviceUrl) to the controller endpoint, assign the document identifier to [`documentPath`](https://help.syncfusion.com/cr/aspnetcore-js2/Syncfusion.EJ2.PdfViewer.PdfViewer.html#Syncfusion_EJ2_PdfViewer_PdfViewer_documentPath), and call `appendTo` to render the control in the container.
+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.
+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.
+
+The following example demonstrates how to load the viewer dynamically after an AJAX request:
 
 ```html
 
@@ -42,6 +44,6 @@ Follow these steps to instantiate the component dynamically:
 
 ```
 
-Ensure that the controller action returns the PDF file or document token expected by the viewer and that the response respects authentication requirements. Dispose of the dynamically created viewer when it is no longer needed to release resources.
+Ensure the controller action returns a valid PDF file path, stream, or base64 string supported by the viewer. For optimal performance, properly dispose of the viewer instance using the `destroy()` method when the container is removed or the document is no longer required.
 
 [View Sample in GitHub](https://github.com/SyncfusionExamples/asp-core-pdf-viewer-examples/tree/master/Common/Instantiate%20PDF%20Viewer%20dynamically).

Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/export-as-image.md

@@ -7,19 +7,19 @@ control: PDF Viewer
 documentation: ug
 ---
 
-# Export pages as images in the ASP.NET Core PDF Viewer
+# Export PDF pages as images in ASP.NET Core PDF Viewer
 
-Export individual pages or a range of pages from a PDF document as raster images using the `ExportAsImage` APIs. These helpers convert pages to bitmaps that you can save, process, or serve for download.
+The Syncfusion<sup style="font-size:70%">&reg;</sup> ASP.NET Core PDF Viewer provides the `ExportAsImage` APIs to convert individual pages or a range of pages into raster images. These images can be saved to disk, processed in-memory, or served as downloads in your application.
 
 ## Steps to export pages as images
 
-**Step 1:** Follow the steps in the [Syncfusion ASP.NET Core PDF Viewer getting started guide](https://help.syncfusion.com/document-processing/pdf/pdf-viewer/asp-net-core/getting-started) to create a simple PDF Viewer application.
+**Step 1:** Create an ASP.NET Core PDF Viewer application by following the [getting started guide](https://help.syncfusion.com/document-processing/pdf/pdf-viewer/asp-net-core/getting-started).
 
-**Step 2:** Choose the appropriate `ExportAsImage` overload to export pages with the required DPI, size, or range settings. The following examples demonstrate each option.
+**Step 2:** Use the `PdfRenderer` class to load the document and invoke the appropriate `ExportAsImage` overload based on the requirements.
 
 ### Export a single page
 
-Exports the specified page as image using the Pdfium rendering engine.
+Convert a specific page to a `Bitmap` using the default rendering settings.
 
 ```cs
 
@@ -34,9 +34,9 @@ bitmapimage.Save(@"currentDirectory\..\..\..\..\Images\" + "bitmapImage" + i.ToS
 
 ```
 
-### Export a page with custom DPI
+### Export with custom DPI or size
 
-Exports the specified page as image with respect to the specified DPI values.
+To control the resolution or dimensions of the exported image, use the overloads that accept DPI values or `SizeF` objects.
 
 ```cs
 
@@ -87,7 +87,7 @@ bitmapimage.Save(@"currentDirectory\..\..\..\..\Images\" + "bitmapImage" + i.ToS
 
 ### Export a range of pages
 
-Exports the specified pages as images using the Pdfium rendering engine.
+Retrieve an array of bitmaps for a specific page range.
 
 ```cs
 
@@ -192,8 +192,6 @@ using (var stream = new FileStream(Path.Combine(@"currentDirectory\..\..\..\..\D
 
 ```
 
-These APIs enable exporting PDF Viewer pages as images for additional processing or download workflows.
+[View complete sample in GitHub](https://github.com/SyncfusionExamples/asp-core-pdf-viewer-examples/tree/master/Common/Export%20as%20Image%20in%20ASP.NET%20Core%206.0/ExportImageindotnet6)
 
-[View Sample in GitHub](https://github.com/SyncfusionExamples/asp-core-pdf-viewer-examples/tree/master/Common/Export%20as%20Image%20in%20ASP.NET%20Core%206.0/ExportImageindotnet6)
-
-N> Ensure the provided document path and the output image save locations are updated to match your application.
+N> Ensure the application has appropriate read/write permissions for the document and image directories. For cross-platform deployments, refer to the [PDFium resolution guide](./resolve-pdfium-issue) to configure native dependencies.

Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/extract-text-option.md

@@ -7,21 +7,20 @@ control: PDF Viewer
 documentation: ug
 ---
 
-# Configure extractTextOption in the ASP.NET Core PDF Viewer
+# Configure extractTextOption in ASP.NET Core PDF Viewer
 
-The `extractTextOption` property controls how text is extracted and optimizes memory usage. It also affects the data returned in the `extractTextCompleted` event. Choose one of the following options to determine the text and layout data to retrieve.
-
-### Available Options:
-
-**None:** No text information is extracted or returned. This is useful when you want to optimize memory usage and don't need any text data.
+The Syncfusion<sup style="font-size:70%">&reg;</sup> ASP.NET Core PDF Viewer provides the [`extractTextOption`](https://help.syncfusion.com/cr/aspnetcore-js2/Syncfusion.EJ2.PdfViewer.PdfViewer.html#Syncfusion_EJ2_PdfViewer_PdfViewer_ExtractTextOption) property to control how the component extracts text data. Adjusting this property allows you to optimize memory consumption and determine the specific metadata returned in the `extractTextCompleted` event.
 
-**TextOnly:** Extracts only the plain text from the document. This option excludes any layout or positional information.
+## Available options
 
-**BoundsOnly:** Extracts layout information, such as bounds or coordinates, without including the plain text data.
+The following values can be assigned to `extractTextOption`:
 
-**TextAndBounds:** Extracts both the plain text and the layout (bounds) information, which is the default behavior.
+*   **None:** Disables text extraction entirely. Use this to minimize memory footprint when text interactions or extraction are not required.
+*   **TextOnly:** Extracts plain text strings only. This option excludes all layout, positional, and coordinate metadata.
+*   **BoundsOnly:** Extracts positional information (bounds) for text elements without retrieving the actual text content.
+*   **TextAndBounds (default):** Extracts both string content and corresponding layout metadata.
 
-The following example demonstrates how to configure the `extractTextOption` property to control the level of text extraction:
+The following example demonstrates how to set `extractTextOption` to `None` in a standalone viewer configuration:
 
 {% tabs %}
 {% highlight cshtml tabtitle="Standalone" %}
@@ -44,16 +43,18 @@ The following example demonstrates how to configure the `extractTextOption` prop
 {% endhighlight %}
 {% endtabs %}
 
-### Description of each option
-**extractTextOption.TextAndBounds (default):** Returns both plain text and positional data (bounds). Use this option when you need both the content of the PDF and its layout for further processing.
+The `extractTextOption` property controls how text is extracted and optimizes memory usage. It also affects the data returned in the `extractTextCompleted` event. Choose one of the following options to determine the text and layout data to retrieve.
+
+### Available Options:
+
+**None:** No text information is extracted or returned. This is useful when you want to optimize memory usage and don't need any text data.
 
-**extractTextOption.TextOnly:** Returns only the plain text from the PDF. No positional data is included. Text search functionality is disabled when using this option; use `findTextAsync` for searching.
+**TextOnly:** Extracts only the plain text from the document. This option excludes any layout or positional information.
 
-**extractTextOption.BoundsOnly:** Returns only layout information (bounds) of the text, excluding the actual content. Useful when focusing on text positions rather than the text itself.
+**BoundsOnly:** Extracts layout information, such as bounds or coordinates, without including the plain text data.
 
-**extractTextOption.None:** Does not extract or return any text or layout information. Use this setting to optimize memory usage when text extraction is unnecessary. This setting applies to the `extractTextCompleted` event and cannot be used with the `ExtractText` method.
+**TextAndBounds:** Extracts both the plain text and the layout (bounds) information, which is the default behavior.
 
-N> Text search: When using the `extractTextOption.TextOnly` or `extractTextOption.None` options, the `findText` method is unavailable. Use the `findTextAsync` method to perform text searches asynchronously.
+N> **Text Search Compatibility:** When `extractTextOption` is set to `TextOnly` or `None`, the standard `findText` method is unavailable. Use the `findTextAsync` method to perform asynchronous text searches in these modes.
 
-Sample: How to configure extractTextOption  
 [View sample in GitHub](https://github.com/SyncfusionExamples/asp-core-pdf-viewer-examples/tree/master/How%20to)

Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/get-page-info.md

@@ -7,15 +7,17 @@ control: PDF Viewer
 documentation: ug
 ---
 
-# Get page info in the ASP.NET Core PDF Viewer
+# Retrieve page information in ASP.NET Core PDF Viewer
 
-Use the `getPageInfo()` method to retrieve information for a specified page, including height, width, and rotation.
+The Syncfusion<sup style="font-size:70%">&reg;</sup> ASP.NET Core PDF Viewer provides the `getPageInfo()` method to programmatically retrieve metadata for a specific page. This metadata includes the page height, width, and current rotation angle.
 
-The following steps show how to use `getPageInfo`.
+Follow these steps to integrate the page information API into your application:
 
-**Step 1:** Follow the steps in the [Syncfusion ASP.NET Core PDF Viewer getting started guide](https://help.syncfusion.com/document-processing/pdf/pdf-viewer/asp-net-core/getting-started) to create a sample.
+**Step 1:** Initialize your 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).
 
-**Step 2:** Use the following code to get the height, width, and rotation for a specified page.
+**Step 2:** Invoke the `getPageInfo()` method using the page index (zero-based) to retrieve the required metadata.
+
+The following example demonstrates how to retrieve and log page details when a button is clicked:
 
 {% tabs %}
 {% highlight cshtml tabtitle="Standalone" %}
@@ -59,6 +61,6 @@ document.addEventListener('DOMContentLoaded', function () {
 {% endhighlight %}
 {% endtabs %}
 
-By following these steps, the page info API can be integrated and used in the ASP.NET Core PDF Viewer.
+The `getPageInfo()` method returns an object containing the spatial dimensions and orientation of the specified page, which is essential for custom layout calculations or rendering overlays.
 
 [View sample in GitHub](https://github.com/SyncfusionExamples/asp-core-pdf-viewer-examples/tree/master/How%20to)

Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/identify-added-annotation-mode.md

@@ -3,17 +3,23 @@ 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.
 platform: document-processing
-control: Identify added annotation mode
+control: PDF Viewer
 documentation: ug
 ---
 
-# Identify added annotation mode in ASP.NET Core PDF Viewer
+# Identify annotation addition mode
 
-The PDF Viewer library allows you to identify whether the added annotations in PDF document is UI drawn, imported or existing annotation. Annotation mode can be identified using the [**annotationAddMode**](https://help.syncfusion.com/cr/aspnetcore-js2/syncfusion.ej2.pdfviewer.pdfviewer.html#Syncfusion_EJ2_PdfViewer_PdfViewer_AnnotationAdd) property of [**annotationSelect**](https://help.syncfusion.com/cr/aspnetcore-js2/syncfusion.ej2.pdfviewer.pdfviewer.html#Syncfusion_EJ2_PdfViewer_PdfViewer_AnnotationSelect) event.
+The Syncfusion<sup style="font-size:70%">&reg;</sup> ASP.NET Core PDF Viewer allows you to verify how an annotation was added to the document. By inspecting the [`annotationAddMode`](https://help.syncfusion.com/cr/aspnetcore-js2/Syncfusion.EJ2.PdfViewer.PdfViewer.html#Syncfusion_EJ2_PdfViewer_PdfViewer_AnnotationAdd) property within the [`annotationSelect`](https://help.syncfusion.com/cr/aspnetcore-js2/Syncfusion.EJ2.PdfViewer.PdfViewer.html#Syncfusion_EJ2_PdfViewer_PdfViewer_AnnotationSelect) event, you can distinguish between annotations that were manually drawn by the user, imported from a data source, or pre-existing in the PDF file.
 
-**Step 1:** Follow the steps provided in the [link](https://help.syncfusion.com/document-processing/pdf/pdf-viewer/asp-net-core/getting-started) to create simple PDF Viewer sample.
+## Implementation guide
 
-**Step 2:** The following code snippet explains how to identify added annotation mode.
+Follow these steps to identify the addition mode of an annotation:
+
+**Step 1:** Initialize 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).
+
+**Step 2:** Subscribe to the `annotationSelect` event and log the `annotationAddMode` property from the event arguments.
+
+The following example demonstrates this implementation across standalone and server-backed configurations:
 
 {% tabs %}
 {% highlight cshtml tabtitle="Standalone" %}
@@ -22,13 +28,13 @@ The PDF Viewer library allows you to identify whether the added annotations in P
     <ejs-pdfviewer  id="pdfviewer"
                     style="height:600px"
                     documentPath="https://cdn.syncfusion.com/content/pdf/form-filling-document.pdf"
-                    resourceUrl="https://cdn.syncfusion.com/ej2/31.1.17/dist/ej2-pdfviewer-lib"
-                    annotationSelect=annotationSelected>
+                    resourceUrl="https://cdn.syncfusion.com/ej2/31.1.17/dist/ej2-pdfviewer-lib">
     </ejs-pdfviewer>
 </div>
 
 <script>
-    function annotationSelected(args) {
+    const viewer = document.getElementById("pdfviewer").ej2_instances[0];
+    viewer.annotationSelect = function annotationSelected(args) {
         console.log(args.annotationAddMode);
     }
 </script>
@@ -40,13 +46,13 @@ The PDF Viewer library allows you to identify whether the added annotations in P
     <ejs-pdfviewer id="pdfviewer"
                    style="height:600px"
                    documentPath="https://cdn.syncfusion.com/content/pdf/form-filling-document.pdf"
-                   serviceUrl="/api/PdfViewer"
-                   annotationSelect=annotationSelected>
+                   serviceUrl="/api/PdfViewer">
     </ejs-pdfviewer>
 </div>
 
 <script>
-    function annotationSelected(args) {
+    const viewer = document.getElementById("pdfviewer").ej2_instances[0];
+    viewer.annotationSelect = function annotationSelected(args) {
         console.log(args.annotationAddMode);
     }
 </script>