The preferred way for developing with a ASP.NET Core Renderer is to host Sitefinity CMS remotely on a shared IIS instance or App Service. This allows you to take advantage of the benefits that the .NET SDK and the ASP.NET Core Renderer– cross platform development, fast startup, fast build time, modern and robust technology stack.
Because in this scenario there are no or little changes to Sitefinity CMS, you can maintain it separately and upgrade it using the Sitefinity CLI.
RECOMMENDATION: We recommend connecting Sitefinity CMS to a replica of the live database, so that you always test your changes against the latest database. This way you focus only on the frontend development, which is very lightweight and fast.
On each development machine, you can run the Renderer either through Visual Studio or Visual Studio Code. You can use any platform, supported by the .NET SDK.
You can run the Renderer either on HTTP or HTTPS.
launchSettings.json
commandName: “Project”
If you want to test multiple sites locally with their live domains, the you can set the default site in the CMS. Alternatively, you can host the Renderer in IIS locally and test the sites there. For more information, see Preview multisite sites locally.
For more information about hosting Sitefinity CMS, see the following:
Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.
This free lesson teaches administrators, marketers, and other business professionals how to use the Integration hub service to create automated workflows between Sitefinity and other business systems.
This free lesson teaches administrators the basics about protecting yor Sitefinity instance and its sites from external threats. Configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.
The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important