Developing sites using ASP.NET MVC

Kentico supports website development using ASP.NET MVC 5. The support is based on a separate MVC application while Kentico functions as separate application that you use as a content platform.

Both Kentico and the MVC application access data from the same database and call API from Kentico libraries. Content synchronization, for example of smart search indexes, is handled by web farms. This approach allows you to separate the live site (MVC application) and the administration (Kentico).

This means that you use Kentico to store data and manage content (mostly via pages), and generate the entire design of the site using your own MVC controllers and views.

Kentico’s Pages application is a repository for content consisting of content only pages. The content itself is entered and modeled by content editors based on a content structure created by developers. Developers take care of how the content is displayed on the live site via the MVC application.

Requirements and limitations

You will need the following configuration for MVC projects:

  • .NET Framework: .NET Framework 4.5 / 4.5.1 / 4.6.
  • Visual Studio: Visual Studio 2013 or higher (for MVC 5 support).

License requirements

You only need to purchase a license for the MVC application. The extra license for the Kentico administration and an extra web farm server is provided for free. See Kentico licensing for MVC applications for further details.

Supported Kentico features

For the list of currently supported Kentico features that you can use when developing sites using ASP.NET MVC, see Supported and unsupported Kentico features on MVC sites.

ASP.NET MVC development process in Kentico

The following section contains a brief overview to get you started with site development using ASP.NET MVC. You can find a more detailed explanation of the covered areas in the linked pages.

  1. Create and set up an MVC application
  2. Define site content structure
    • In Kentico’s Pages application, create a content structure based on the individual content only page types you are using in your MVC application.
  3. Develop the MVC application
  4. Deploy your MVC application