We have an ASP.NET WebForms application running on .NET Framework 4.8 and have implemented your Viewer solution using the provided code base from GitHub. However, we are experiencing slow performance when loading and displaying documents. It takes a considerable amount of time for the information to be rendered.
Our current configuration includes:
In-memory cache
Loading the first 10 pages initially
Given this setup, what optimizations or best practices would you recommend to improve performance?
Additionally, we are considering integrating your Editor solution in the future. Could you provide guidance on the best implementation approach considering our tech stack? Furthermore, how would the licensing work when using both the Viewer and Editor solutions together?
We appreciate your support and look forward to your recommendations.
Thanks you for your interest in GroupDocs.Viewer and Editor!
To answer on your question more precisely, we need some sample files on which you’re experiencing slow performance. We will check them on our side and determine whether the performance can be improved by some combination of options and approaches, applied to the “GroupDocs.Viewer for .NET ASP.NET Web Forms Demo” project, or it is a bug and should be fixed on our side in the GroupDocs.Viewer codebase, or maybe this is a complex file and its performance cannot be improved, unfortunately.
Regarding integrating the GroupDocs.Editor — again, we need more details to give you a complete answer, but keep in mind that when the GroupDocs.Viewer is focused to display the document content in the most accurate way, and it supports rendering the document to the PDF, HTML, JPEG and PNG, the GroupDocs.Editor can render the document only to the HTML format and it is focused to make the document editable on the client-side in any HTML WYSIWYG-editor, and this is its 1st priority, while the accuracy of the document representation is a 2nd priority.
Regarding the licensing — you can freely use both GroupDocs.Viewer and GroupDocs.Editor in a single project, they are fully compatible. GroupDocs.Viewer and GroupDocs.Editor have a similar licensing mechanism — you instantiate a License class and then provide a license file by path or by a stream using a SetLicense method. However, your *.lic license file for the GroupDocs.Viewer will not work for the GroupDocs.Editor, you need another one, purchased especially for the GroupDocs.Editor.