Document Studio .NET
Next-generation .NET compliant multi-format document viewing & processing suite for .NET developers

Compatibility

Visual Studio 2013/2015/2017/2019

Home » Newsletter » May 2016

By Shivaranjini & Pradeep

In order to help investigate document loading and server connectivity issues we have introduced logging for the operations of the ASP.NET Document Viewer. The Document Viewer emits these log messages to the console window of the client browser only when logging is enabled. Logging can be enabled on the client-side based on need.

To simplify the process of logging we have introduced a class called logger. Currently it supports logging at “INFO” and “ERROR” levels and it writes log messages on the console window of the browser.

To enable logging at “INFO” level, set the following property to true:

    logger.infoLogsEnabled  = true;

To enable logging at “ERROR” level, set the following property to true:

    logger.errorLogsEnabled  = true;

This can be enabled while initializing DocumentViewer control

    gnostice.logger.infoLogsEnabled  = true;
    var documentViewer = new gnostice.DocumentViewer('doc-viewer-id');

or it can also be done in console window of the browser. With this approach the user need not have to change their web application code.

The following screenshot shows how logging can be enabled from the browser console window and what the log messages look like.

Related articles:

• Display server-side documents in ASP.NET Web Viewer control

• The New ASP.NET Document Viewer control for displaying DOCX, DOC, PDF and images (BMP, JPEG, PNG, TIFF)

• The New ASP.NET Document Viewer control for displaying DOCX, DOC, PDF and images (BMP, JPEG, PNG, TIFF) in ASP.NET MVC Application

• Working with the new ASP.NET Document Viewer control in TypeScript projects

• Search text on images with Document Studio .NET's ASP.NET Document Viewer

• Print without preview using Document Studio .NET's ASP.NET Document Viewer control