Installing Quicksilver

Note: The Installing Quicksilver video illustrates the installation steps below.


  • An instance of SQL, either on the server or another computer.
  • An Active Directory user with dbcreator role on the SQL instance to run the database install.
  • SQL Management Studio on the computer to which you are installing Quicksilver. Needed to run the setupdatabases.cmd file.

Download the Quicksilver project

  1. Download the Quicksilver project from GitHub: Place the files anywhere in your file system.
  2. Give the user who will build the project full control over the Quicksilver folder.
    1. Right click the Quicksilver-master folder.
    2. Click Properties.
    3. Click the Security tab.
    4. Click Edit.
    5. Click Add.
    6. Enter your username, since most likely you will give the user full control.
    7. Give that user full control permissions.

Add the Optimizely NuGet package feed to Visual Studio

  1. Open Visual Studio > Tools > NuGet Package Manager > Package Manager Settings > NuGet Package Manager > Package Sources.
  2. If not already done, add the Optimizely NuGet package source

Set Quicksilver as the startup project

  1. From Visual Studio, open the Quicksilver solution file: folder to which you saved QuickSilver/Quicksilver-master/Quicksilver.sln. The project is loaded into Visual Studio.
  2. Open Visual Studio Solution Explorer, right-click the solution, and click Properties.
  3. Choose Common Properties > Startup Project > Single startup project and set the drop-down to EPiServer.Reference.Commerce.Site. This causes the Commerce site to load when you start debugging.
  4. Build the solution.

Note: If you want to access the CMS and Commerce Manager sites, select multiple startup and set both EPiServer.Reference.Commerce.Site and EPiServer.Reference.Commerce.Manager to start up (with or without debugging).

Update SetupDatabases.cmd with database and user information

The SetupDatabases.cmd file creates two databases and an SQL account to connect to the database.

Note: If you are installing the Quicksilver database to a non-local SQL Server, the Windows user who will run SetupDatabases.cmd must be added to the SQL Server and given the DBCreator role.

  1. Using a text editor, open the folder to which you saved QuickSilver/Quicksilver-master/Setup/SetupDatabases.cmd file.
  2. In that file, review the following statement to specify the database instance.
    set sql=sqlcmd -S . -E
    • This is the default command which sets the database server to '.' meaning the SQL Server is on the same machine as the installer. No instance is specified after the ‘.’ but it could be set to any instance desired, for example .\MyInstance.

    • ‘-E’ means the user running the installer will create the database, so there is no need to specify a username and password. Note that for ‘-E’ to work, mixed mode authentication must be present on the server. If mixed mode authentication is not preferred or available, then SQL authentication (using a username and password) can be chosen by using ‘-U’ (the username) and ‘-P’ (the password) instead of ‘-E’.

      Example 1:

      In this example, change the set sql statement to the following: 

      set sql=sqlcmd -S SQLServerName\SQLInstanceName -U username -P password

      Example 2:

      For this example there is an instance called SQLExpress on the same machine as the Quicksilver solution, and we want to use the user running the setup to create the database:

      set sql=sqlcmd -S .\SQLExpress -E

      Change the command to set the preferred SQL machine\instance and authentication.

  3. Save the SetupDatabases.cmd file.

Update web.config file with user and database name

Note: This step is only necessary if you changed values in Update SetupDatabases.cmd, as described in Update the SetupDatabases.cmd file with database and user information.

  1. To change the user and database name in the connection strings, return to Visual Studio, go to Solution Explorer > EPiServer.Reference.Commerce.Site > web.config. Then, modify the two connection string settings to the intended database name, SQL server, and user.
      <clear />
      <add name="EPiServerDB" connectionString="Data Source=EPUSLPTBOBO\SQLEXPRESS;Initial Catalog=Quicksilver.Cms;Integrated Security=False;User ID=Quicksilver;Password=Optimizely15;MultipleActiveResultSets=True" providerName="System.Data.SqlClient" />
      <add name="EcfSqlConnection" connectionString="Data Source=EPUSLPTBOBO\SQLEXPRESS;Initial Catalog=Quicksilver.Commerce;Integrated Security=False;User ID=Quicksilver;Password=Optimizely15;Connect Timeout=10;Application Name=ECApplication" providerName="System.Data.SqlClient" />
    • If you are using SQL Express locally, change Data Source=. to Data Source=.\SQLExpress
    • Otherwise, modify the connection strings to reflect the intended location of the Quicksilver.Cms and Quicksilver.Commerce databases. For example, Data Source=SQLServerName\SQL2014.
  2. Make these changes for the lines that begin with <add name="EPiServerDB" and <add name="EcfSqlConnection".
  3. Repeat these steps for the EPiServer.Reference.Commerce.Manager > web.config file.

Create the databases

  1. Run Setup\SetupDatabases.cmd to create the databases. The AD user running the command must have the dbcreator role on the SQL instance.

    Note: Do not use the Run as administrator option.

View the site

  1. Press F5 to load the site.
  2. An EPiServer Commerce Migration page might appear. If so, follow the directions.
  3. The QuickSilver site opens.
  4. Log in using the credentials username: password: store.

Last updated: Jan 26, 2021