Last updated: Dec 01 2016

Installing Episerver

This topic describes a first-time installation of an Episerver CMS website with the latest updates and with or without sample templates, Commerce, Find and other add-ons (optional).


The following components are needed to follow the instructions on this page:

  • Microsoft Visual Studio for installing and updating Episerver. 
  • Episerver Visual Studio extensions which are a full set of templates for MVC and Web Forms to get a jump-start when developing websites. Download and double-click the file to run the installation, or install directly from Visual Studio (Community, Professional or Enterprise) as described below. An extension package is available for each Visual Studio version.
    1. To install from Visual Studio, select Tools Extensions and Updates.
    2. In the extensions window, select Online, and type "episerver" in the search box.
    3. Select Episerver CMS Visual Studio Extension and click Install (or Update if already installed).
  • The Episerver NuGet feed source added to your Visual Studio. Needed to add Commerce, Find and other add-ons to your solution, and to upgrade your project with the latest. See Installing Episerver updates on how to add a NuGet feed.

Note: You can order a time-limited demo license for evaluation purposes, see Episerver License Center. (A license is not required when using IIS Express.) You need a commercial Episerver license for testing and production environments. 

Installing CMS

Install an Episerver CMS website, empty or with the "Alloy" sample templates (MVC/Web Forms).

Note: Installing Episerver is a video that shows you how to install an Alloy sample site.

  1. Open Visual Studio and select File > New > Project.
  2. Select Templates > Visual C# > Episerver > Episerver Web Site and provide a name. Click OK.
  3. Select Alloy (MVC/WebForms) to create a site with sample content, or Empty for a site without templates.
  4. Select a search option:
    • For an Alloy site, select Episerver Find, or Episerver Search to use the built-in basic search.
    • For an empty site, the Configure Search option is disabled, and no search will be installed. You can add Episerver Find or Episerver Search later if desired.

  5. The project is created. When finalized, build and open the website in a browser.
  6. Log in to the site:
    • For an empty site, add /episerver to the site URL, and log in using your Windows credentials.
    • For Alloy MVC, you will be prompted to create an administrator account (site is using ASP.NET Identity). Provide the account credentials, click register and you will be logged in.  
    • For Alloy WebForms, select the Log in link at the bottom of the start page, and log in using your Windows credentials. Note that you must be local admin on the server you are running Episerver on. If not, create a new local user with admin rights under Control panel > Local Users and Groups, and log in using that account.

Installing Commerce

Empty Commerce site

These steps install an empty website with CMS and Commerce. See below if you want to install a Commerce site with sample templates. Note that a Commerce installation consists of two sites (front-end/back-end).

  1. Follow the steps 1-4 above to create an empty CMS site. This will be the front-end site project.
  2. Expand the project, right-click on References and select Manage NuGet Packages
  3. Browse the Episerver package source to locate the Episerver Commerce packages.
  4. Install the EPiServer.Commerce and EPiServer.Commerce.UI.ManagerIntegration packages, to add the Commerce components to the front-end site.
  5. To create the back-end parts, right-click on the solution and select Add > New > Project. Under Visual C#, add a new project of type ASP.NET Web Application. (name the sites so they are easily distinguished). 
  6. Click OK to continue, and select Empty in the template selection step next (skip the Configure MS Azure Web App step if prompted for this).
  7. On the back-end site project, right-click on References and select Manage NuGet Packages.
  8. Browse the Episerver package source to locate and install the EPiServer.CommerceManager package. This adds the Commerce Manager components to the back-end site project.

  9. In the Package Manager Console, select the front-end site and run the command update-epidatabase.

  10. Start the front-end site (Ctrl + F5), and when prompted log in using the default credentials admin/store (remember to change these later). 
  11. Follow the instructions to execute the remaining migration steps.
  12. When the migration has finalized, verify that you can access the edit and admin views using http://yoursite/episerver or http://localhost:../episerver. If you have difficulties accessing Commerce Manager from edit view, right-click on that project in Visual Studio, and select Set as StartUp Project. Start the Commerce Manager site and log in. Then make the front-end project start-up project again.

Commerce site with sample templates

The Quicksilver Commerce sample site and installation instructions are available for download from GitHub.

Installing Find

For information about adding Find to your Episerver website, see Creating your project in the Get started with Find section.

Episerver Commerce-Find integration

This integration adds specific functionality when using Find with Episerver Commerce. If you want to install this on your website, the Find content indexing job needs to be run on the site after the EPiServer.Find.Commerce package has been installed. See Episerver Commerce-Find integration.

Installing other add-ons

You can extend Episerver through add-ons available for a wide selection of areas, as examples: analytics, search optimization, and marketing automation. Most add-ons are installed as NuGet packages, but other options exist. See Episerver add-ons and Installing add-ons.

Note: If you want to install CMO on a new project with the latest version of CMS, start by installing an Episerver 7.5 site with CMO 7.5 using Deployment Center, then gradually upgrade to the latest CMS and CMO versions by installing and upgrading NuGet packages in Visual Studio. When upgrading from CMS 7.5 to CMS 8, follow the instructions in Upgrading CMO with CMS 8 to move the CMO resources from the old location used previously to a new location under the /modules/_protected folder.

Related topics


Note: From versions higher than 7.5, the Episerver platform is installed and updated through Visual Studio and NuGet packages.

Installation instructions for version 7.5 and lower
(select appropriate version):

Episerver CMS
Episerver Commerce
Episerver Find