Installation questions and answers

This page answers common questions and issues encountered when installing Xperience projects.

What .NET version do created project templates target?

Projects created by the installation process always target the minimum supported .NET version as specified in the system requirements. You need to ensure the target machine has the required version installed. 

Can I change the Target framework version of installed projects?

Yes. You can increase the Target framework of installed Xperience projects to a higher .NET version.

  1. Open the project in Visual Studio.
  2. Manually change the Target framework version.

If you update the Target framework version for a project, we also recommend consolidating all installed NuGet packages to target the same version:

  1. In Visual Studio, open the Package Manager Console (under Tools > NuGet Package Manager).

  2. Run the following command:

     Update-Package -reinstall;

The Update-Package command reinstalls all NuGet packages with the appropriate target framework version for your project.

What if I do not install the database with my web project?

Without a database, your web project cannot function at all. You need to have an SQL server available before you begin the installation process. See the System requirements for a list of supported servers.

How can I access my LocalDB database through Microsoft SQL Server Management Studio?

Use the (localdb)\Kentico server name. The database files (xperience.mdf, xperience_log.ldf) are physically stored in your user’s profile (e.g., C:\Users\Andy\).

Which starter project should I install?

If you wish to develop a new website, use the Boilerplate ( kentico-xperience-mvc ) project template. If you wish to evaluate the system or examine a sample implementation of an Xperience site, install the Dancing Goat ( kentico-xperience-sample-mvc ) sample site.

Where can I find the installation log?

Xperience sites are installed as new project templates using the .NET command-line utility. The tool doesn’t provide logging support. However, any irrecoverable errors that occur during installation terminate the installation process and the terminal displays a message detailing the issue.

For logging, e.g., inside deployment scripts or similar places where manual supervision is unlikely, you can pipe command output to a physical file. For example, using PowerShell’s Out-File cmdlet. 

Where can I get more information?

You can contact our support department, who will be happy to assist, at