Error handling and Logging

By default, the ASP.NET Core Renderer catches exceptions thrown by widgets and isolates them on the widget level.

Errors in widget are rendered in following ways:

• When editing a page - the widget error is displayed in the page editor. 
• When previewing or viewing a page – the widget does not render any content.

This way, the Renderer does not allow a single widget to break the entire page.

When in development mode, the ASP.NET Core Renderer takes advantage of the DeveloperExceptionMiddleware that comes automatically included in the pipeline.

Error pages handling

Because the ASP.NET Core Renderer is a standalone application, the error handling is separated from the configuration of Sitefinity CMS. Therefore, any settings for error handling that you make in Sitefinity CMS do not affect the ASP.NET Core pages, only the MVC-based pages. 

Configure error pages 

There are no custom configurations for error pages handling. NET Core Renderer relies on the out-of-the-box implementations of ASP.NET Core for error handling. 

For more information, see Handle errors in ASP.NET Core.

GITHUB EXAMPLE: The Error pages sample, located in Sitefinity GitHub Repository illustrates how to use the following middleware:

• ErrorHandlerPage
• UseStatusCodePages

Sitefinity ASP.NET Core Renderer implements the standard approach for logging in ASP.NET Core.
For more information, see Logging in .NET Core and ASP.NET Core.

GITHUB EXAMPLE: The GitHub sample mentioned above, contains a sample implementation of a third-party logging library - Serilog.