Skip to main content
.NETFramework4.6.1.NETStandard2.0

The GrapeCity.Documents.Pdf.ViewerSupportApi package implements the server-side Support API for GcPdfViewer (https://www.npmjs.com/package/@grapecity/gcpdfviewer).

Published
Sep 20, 2024
2y ago
Total Downloads
47.1K
47,070

Install

dotnet add package GrapeCity.Documents.Pdf.ViewerSupportApi --version 7.2.2
ProductVersions
.NET Standard
netstandard2.0
Other
.NETFramework4.6.1

README

GrapeCity.Documents.Pdf.ViewerSupportApi

Please refer to the note below for important package information.

The GrapeCity.Documents.Pdf.ViewerSupportApi package implements the server-side Support API for the GrapeCity Documents PDF Viewer (GcPdfViewer), and can be used in ASP.​NET Core and Web Forms projects. GcPdfViewer is a JavaScript client-side control that is available on npmjs. It is a part of the GrapeCity Documents for PDF product. GcPdfViewer can be used as a powerful client-side only PDF viewer. If connected via Support API to a backend running GcPdf on the server, the viewer enables:

  • Customizable and mobile-friendly PDF form filler
  • Real-time collaborative editing mode
  • Annotation and form editors
  • Quick edits using secondary toolbars
  • PDF redaction
  • Signature verification
  • Predefined stamps
  • Other editing features

The full source code of this library together with C# demo projects for ASP.​NET Core and Web Forms is included in the src/ folder in this package. The WEB_FORMS constant is defined for the Web Forms target.

Resources

GrapeCity Document APIs

A Shift from ‘GrapeCity Documents' to ‘Document Solutions' for US Edition

重要信息:对于 ’GrapeCity Documents’ 中国版本,组件名已经更改为 ‘GcDocs’。

GrapeCity Documents has undergone a marketing rebranding and as a result, the v7.2 Maintenance release in November 2024 will mark the final release under the old GrapeCity Documents product branding.

Starting with version 8.0.0 onwards, the packages will only be released using the new package names and this GrapeCity package will be phased out.

It is highly recommended to update to these new packages as soon as you can. Transitioning to the new packages has been simplified through the Documents Migration tool, conveniently included in the product trial download zip files available for the respective products:

Please note that despite the adoption of new package names, the APIs, namespaces, and type names remain unchanged. You will not need to modify your code. Only the package names and DLL names have been changed, just requiring updates to the new package references.

Existing subscriptions will continue to receive the new package updates. If you have any questions or need any assistance with this update, please contact our support teams. Please find the nuget package links for new packages below:

Changes from Previous Version

No structural changes between v7.2.1 and v7.2.2.

Adoption Assessment

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.Compatibility metadata lists 2 target frameworks; confirm the exact target used by your application.The published metadata declares 21 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.

Related Guides & Workflows

Learn how to evaluate, integrate, or audit this package in your .NET project.