Kentico Xperience 13 documentation and ASP.NET Core

Most documentation about running Xperience applications under ASP.NET Core can be found in a dedicated section: Developing Xperience applications using ASP.NET Core. The rest of the documentation still applies, but some code samples and scenarios might need slight modifications for Core projects.

All major differences between the MVC 5 and Core platforms are summarized in Migrating to ASP.NET Core.

×

Xperience development models

Xperience provides two distinct development models – ASP.NET MVC 5 (referred to as MVC) and ASP.NET Core (referred to as Core).


ASP.NET CoreASP.NET MVC 5
Technical propertiesWith both development models, websites consist of two applications – an administration application and a live site application. The two applications use a shared database and are synchronized using a web farm mechanism.
  • Based on an open-source framework
  • Cross-platform support
  • Lightweight framework with superior performance
  • Worse support for 3rd party libraries due to being fairly new
  • More available options for 3rd party library integration
  • Stable and established framework
Future compatibilityThe Core development model will be the only option supported in the next generation of Kentico Xperience. We recommend using the Core development model for any new projects.The MVC 5 development model will not be supported in the future. Any existing projects will need to be migrated to ASP.NET Core.
Supported functionality

The majority of Xperience features is available for both development models. However, certain features work differently or are unavailable due to the technical nature of the underlying framework.

All important differences between the development models are described in Migrating ASP.NET MVC 5 projects to ASP.NET Core.

Additionally, External utilities, such as the Xperience installer or Hotfix utility, are not based on ASP.NET Core and cannot run cross-platform (only on Microsoft Windows systems).

Working with contentFor end-users, such as content editors and copywriters, there is no noticeable difference between the two development models. The way of working with content and the tools available are identical.

Documentation structure

All pages in the documentation not specifically targeted at Core are written for the MVC development model. The standard documentation applies to Core scenarios most of the time, but certain steps and code samples may need to be slightly adjusted.

Development using ASP.NET Core is documented in a dedicated section: Developing Xperience applications using ASP.NET Core.

The most important differences between the development models are highlighted on the Migrating ASP.NET MVC 5 projects to ASP.NET Core page.


Was this page helpful?