In this mode, Sitefinity can have both ASP.NET Core and MVC pages.
RECOMMENDATION: We recommend using this mode to migrate MVC to ASP.NET Core pages. For more information, see Migrate from MVC to ASP.NET Core.
The following article describes how to install and setup Sitefinity CMS to work with a standalone ASP.NET Core application as renderer.
You first install and configure Sitefinity CMS to work with the Renderer, then install the Renderer NuGet packages in an ASP.NET Core application, and finally, make the required configurations in the Renderer.
NOTE: To install Sitefinity CMS using NuGet, you must use Visual Studio 2017 or later. This article uses Visual Studio 2019 as a reference.
To install Sitefinity CMS in a blank web application using a NuGet package, perform the following:
To do this, perform the following:
In Visual Studio, perform the following:
Telerik.Sitefinity.All
Progress.Sitefinity
NOTE: With these commands, you install the latest patch build. If you want to install a specific version, you must use the command followed by -Version and the version number. For example, enter Install-Package Telerik.Sitefinity.All -Version 14.4.8100.0
-Version
Proceed by adding any of the desired additional Sitefinity CMS modules. For more information, see Work with decoupled modules.
After creating and configuring your ASP.NET Core application, you have to configure your Sitefinity CMS. Perform the following:
You install the Renderer in a separate ASP.NET Core application. If you do not have one, create it in the following way:
In your Renderer application, you must install the provided NuGet packages:
Progress.Sitefinity.AspNetCore.nupkg
Progress.Sitefinity.AspNetCore.Widgets.nupkg
Progress.Sitefinity.Renderer.nupkg
Progress.Sitefinity.RestSdk.nupkg
Progress.Sitefinity.AspNetCore.FormWidgets.nupkg
Perform the following:
After you have created the project and installed the NuGet packages, you must configure it to connect it to Sitefinity CMS. In Visual Studio, perform the following:
appSettings.json
The file should look in the following way:
Program.cs
launchSettings.json
"commandName": "Project"
applicationUrl
The property should look in the following way: "applicationUrl": "https://localhost:5001;http://localhost:5000"
NOTE: To debug your solution, you need to use the profile you have configured. Debugging of the IIS Express profile is not supported.
To run the Renderer, navigate to https://localhost:5001/Sitefinity or http://localhost:5000/Sitefinity
NOTE: You use these URLs to run the Renderer locally for development purposes. To setup the Renderer for production, you can use on of the hosting scenarios, described in Hosting configurations.
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