When troubleshooting on a live environment, you would do not have the source code of the application deployed.
Problems: If you encounter any of the following problems:
Solution: The above problems are most likely related to incorrectly setup of the .NET Core Renderer application. To fix them, make sure that your Sitefinity CMS instance and your .NET Core Renderer application are correctly set up. Make sure you perform correctly the steps in the Setup procedure.
Solution: Alternatively, you can get more detailed information whether the .NET Core Renderer is set-up correctly, using the Diagnostics section below.
Problem: You are having runtime errors
Solution: You can search the cause of the errors in the logs of the application. To do this, you must access the logs in one of these ways:
If you cannot identify the reason why your Renderer app is not working, you can run the diagnostics page.
NOTE: You should enable this setting only for debugging purposes.
Sitefinity .NET Core Renderer supports diagnosing the page for performance problems.
For page diagnostics, you do not have to setup Sitefinity CMS, using the procedure above.
PREREQUISITES: You must be in development environment
To diagnose a page, you must include the ?sfdiagnostics query parameter in the page URL.
A value for the query parameter is not required.
RESULT: When the page is executed with the query parameter, each widget is profiled for the requests made through the HttpClient interface. The time for the widget execution is logged as well.
The following screenshot displays a sample result:
In the example above, you can see the following:
NOTE: The times are fast, because the data was fetched in the preparation stage, prior to executing the page.
Sign up for our free beginner training. Boost your credentials through advanced courses and certification. Register for Sitefinity training and certification.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important