Last updated: May 15 2018

Installing Quicksilver

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

 

Prerequisites

  • 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

Download the Quicksilver project

  1. Download the Quicksilver project from github: https://github.com/episerver/Quicksilver. 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 Episerver Nuget package feed to Visual Studio

  1. Open Visual Studio > Tools > Nuget package manager > Package manager settings > Nuget package manager > Package Sources.
  2. Add the following 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.

Update SetupDatabases.cmd with database and user information

The SetupDatabases.cmd file creates two databases and a 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

    By default, the database server is set to '.', which means that no SQL instance is specified. If the full version of SQL Server is installed on the local machine, and there is no named SQL instance, do not change the set sql command. Otherwise, change the command to identify the preferred SQL machine and instance.

    If you are using SQL Express locally, specify the following command.

    set sql=sqlcmd -S .\SQLExpress -E
  3. In the SetupDatabases.cmd file, review the highlighted text to specify a username and password
    set sql=sqlcmd -S SQLServerName\SQLInstanceName -U username -P password

    If mixed mode authentication is not enabled or you want to use a SQL user, provide a username and password. Otherwise, leave the command as is.

  4. Save the SetupDatabases.cmd file.

Update connectionStrings.config files 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.Manager > connectionStrings.config. Then, modify the two connection string settings to the intended database name, SQL server, and user.
    <connectionStrings>
      <clear />
      <add name="EPiServerDB" connectionString="Data Source=EPUSLPTBOBO\SQLEXPRESS;Initial Catalog=Quicksilver.Cms;Integrated Security=False;User ID=Quicksilver;Password=Episerver15;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=Episerver15;Connect Timeout=10;Application Name=ECApplication" providerName="System.Data.SqlClient" />
    .
    </connectionStrings>
    
    • 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.Site > connectionStrings.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. Login using the credentials username: admin@example.com password: store.