Hi Tracy,
Thanks for taking interest in GroupDocs.Viewer API.
Yes, you can render the document containing 500+ pages with GroupDocs.Viewer API. However, the document rendering time depends upon multiple factors i-e text, images, tables, graphics etc. and therefore this time can vary for every document. Hence, multiple documents with same number of pages may take different time to get rendered.
Secondly, the search feature is not provided by the back-end GroupDocs.Viewer API. However, it is implemented in our open source document viewer applications.
We shall be waiting for your feedback. Have a nice weekend ahead.
Warm Regards
Thank you for the information. I am just the researcher on this project for my VP. I do not know yet how we will be implementing.
The other question he would like to know to determine if your product could be one that we would like to look at further is do you all support native rendering of Microsoft Office products? And if so, do we need to stand up a MSO server?
Thank you, Tracy
Hi Tracy,
Thanks for your response,
Yes, native document rendering is supported by GroupDocs.Viewer API. In this case, stream returned by GetFile() or GetPdfFile() method must be included/written in the header of HttpContext’s response. After the client app receives this response, it depends on the browser whether it supports to display that file format or not.
In case, the browser does not support all the office format, the file will be downloaded automatically. For this, you will have to maintain your MSO Server. To read more about supported formats, please visit
Supported Formats.
In case of any confusion, feel free to contact us.
Warm Regards