With Sitefinity SaaS setup, Sitefinity CMS is provided as a service and is fully managed by Progress Software. This means that code customizations can be made only through the ASP.NET Core Renderer project.
The project’s code files can be accessed from the Repos section on the Management Portal. You can clone the repository for local development.
To set up a ASP.NET Core Renderer project on your local development environment, follow these steps:
main
After you have cloned the repository locally, you must configure the ASP.NET Core Renderer application to connect to Sitefinity CMS. In Sitefinity SaaS, you can connect your local ASP.NET Core Renderer application only to a non-production cloud environment, which in this case is Staging. When you connect your local ASP.NET Core Renderer application to a Sitefinity CMS application instance hosted in the cloud, you must configure the LocalValidationKey property of the ASP.NET Core Renderer application. Your local Renderer application will send the LocalValidationKey with each request. When the HTTP request reaches the cloud-hosted ASP.NET Core Renderer application, it will compare the incoming LocalValidationKey with its own RemoteValidationKey. If they match, then the setup will be successful, and you will be able to develop locally against the cloud-hosted version of application.
LocalValidationKey
RemoteValidationKey
To configure the LocalValidationKey property of the ASP.NET Core Renderer application, perform the following:
appsettings.json
“Sitefinity”
To run the ASP.NET Core Renderer application on the local environment, navigate to https://localhost:5001/Sitefinity or http://localhost:5000/Sitefinity.
https://localhost:5001/Sitefinity
http://localhost:5000/Sitefinity
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important