Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket


See the [SDK release notes section](πŸ”—ο»Ώ) to learn about current versions and features.

## Configure Optimizely NuGet source in Visual Studio

NuGet packages are available on [https://nuget.optimizely.com](πŸ”—ο»Ώ), which does not require authentication.

  1. Go to **Visual Studio** > **Tools** > **Options** > **NuGet Package Manager** > **Package Sources**.

  2. Click **Add**:

    1. **Name** – Configured Commerce

    2. **Source** – [https://nuget.optimizely.com/feed/packages.svc](πŸ”—ο»Ώ)ο»Ώ

  3. Restore packages.

## Configure the local environment

Open **Visual Studio** and rebuild the solution.

For SQL, follow these steps:

  1. Create a database within sql server

  2. Run `./database/Insite.Commerce.StartingDatabase.sql` against the database.

  3. Optionally run `./database/Insite.Commerce.SampleData.sql` against the database.

  4. Update `./src/InsiteCommerce.Web/config/connectionStrings.config` so it can connect to your new database. `connectionStrings.default.config` is copied to `connectionStrings.config` during a build. If you skipped step 1, you can copy the file manually.

For IIS, follow these steps:

  1. Add a new site to IIS, pointing to `./src/InsiteCommerce.Web`.

  2. Set up bindings:

    1. For simple setups, using a non-standard port like 8080 is fine. The site can then be accessed at `http://localhost:8080`.

    2. If dealing with multiple projects, it can help to have them setup with hostnames on port 80: `projectA.local.com` `projectB.local.com` This requires entries in `c:\Windows\System32\drivers\etc\hosts`: `127.0.0.1` `projectA.local.com` `127.0.0.1` `projectB.local.com`

      Note

      `https` is not required.

Once finished with either set of steps, log in to `/admin` with the following credentials: **user** – admin **password** – admin123