We recommend that you maintain 3 functional types of installs:
Live Site: This is your public-facing live site.
Staging Site: This is a copy of your live site, usually installed on a separate server. Modifications should be deployed and reviewed here before pushing them to the live site, to protect your live site from issues and down time.
Development Site: This is where skinning or code modifications should be made initially. This install is generally the one connected to a source control repository, and is usually installed on one or more developers' local computers. Changes made here should be deployed to the staging site for testing before 'going live'.
Install 3rd-Party Requirements
The following 3 sections cover the installation of 3rd-party software required for the AspDotNetStorefront software to run.
Most Windows Server installations will already have .NET framework 4.5 installed. You can verify the installation choosing Programs and Features from Windows Control Panel / Programs. If .NET Framework 4.5 is installed, you will see it listed; otherwise you can download and install it from Microsoft's site at http://www.microsoft.com/en-us/download/details.aspx?id=30653.
Also be sure to install this Windows component for the WSI interface:
Microsoft SQL Server Configuration
See this page for instructions on installing the database components.
Installing AspDotNetStorefront Software
The first step in installing the AspDotNetStorefront software is to get the files in place on your machine.
The download file is a self-extracting executable. Once the download has completed, double-click the file and follow the prompts to extract the files to your hard drive. The default location for sites in IIS is C:\inetpub\wwwroot but you can put them elsewhere if preferred.
Follow these directions to install a license key (starting with version 10.0.5 there is no need to install a license key file, but the same permissions will be required on the \Images folder).
IIS pretty much handles file permissions for websites on its own through the ApplicationPoolIdentity user. If you run into any issues with file permissions during use of the software (unable to save images, encrypt the web.config, etc) then your host or server administrator has likely changed the user account under which your site runs. The server administrator must give that renamed user account Read/Write/Modify access to the web/Images folder (and starting with version 10.0.19 also provide Modify permissions to the web/Skins folder).
Next, you need to create the database in which the software will store your data.
Note: The figures in this section depict a standard SQL Server Management Studio installation with no extra security measures in place. Your screens may look slightly different depending on the setup and security policies used by your administrator or hosting provider.
Open Microsoft SQL Server Management Studio and log in with the credentials given to you by your system administrator or host or which you created while installing your own SQL Server instance.
Right-click on Databases in the tree view, then click New Database.
Enter a database name, then click OK.
Click the + next to Databases and your new database should show in the list. Click on it to highlight it, then click File -> Open -> File. Navigate to the /db folder where you just extracted the new storefront files, and double click the ‘Create AspDotNetStorefront Database’ file.
Click the Execute button.
Let the script run until it completes. At the bottom of the window you should see a 'Query executed successfully' message. If you see 'Query completed with errors', scroll through the Messages window and find any text in red, and send it to the Support team in a new ticket for assistance.
Navigate to the /web folder where you extracted the storefront files, then open the AppSettings.config file in a text editor such as Notepad or Notepad++. (NOTE that this file is in the web/Config-Internal folder in recent versions)
Find this line and change ‘TBD’ to your own EncryptKey value. The value can be any combination of letters and numbers, and should be at least 8 characters. The application will not run until you change this value.
<add key="EncryptKey" value="TBD" />
In the same /web folder, edit in a text editor the ConnectionStrings.config file to make the following changes:
Data Source – This is the server/instance name where SQL is installed. If installing on a local server, this will often be simply ‘localhost’ or the machine name (check the value in your SQL Server Management Studio app).
Initial Catalog – This is the name of the database you created in step 3, above.
User Id – The ID used to connect to the database. This MUST be a user with full system administration (sysadmin) rights. Typical local installs will use the "sa" account setup when the instance was created.
Password – The password used to connect to the database
This information was all set up during the SQL Server install you did earlier. If SQL Server was already installed on your computer, your host or server admin will have to provide the information. AspDotNetStorefront cannot tell you what to use for these values.
Save your changes.
The last step in the install is configuring IIS. Note: Your server admin or host may have to provide additional steps for this portion of the install, depending on the server configuration. These steps cover a basic install.
First, open IIS Manager and expand the tree to view the folders under Default Web Site:
Right-click on Default Web Site, and click 'Add Application'.
Enter a name for your site in the Alias field. This will be the virtual directory name you access the site at on your computer (e.g. http://localhost/myalias).
Click the ‘…’ button and use the browse window to select the folder that contains the web.config file you modified earlier (this is the /Web folder as delivered). Click OK.
Right-click the application you just added under Default Web Site, click 'Manage Application', then ‘Browse.’ Your site should open in a new browser window – installation is complete! You can access the admin console by adding /admin to the URL opened when you clicked Browse. Refer to Manage Admin Users for more information.
NOTE: An alternative here is to Right-Click "Web Sites" (or "Sites") and choose Add Website, set a Site Name (this is internal to IIS only), choose an app pool or create new one (.net v4.5/4.0 Integrated), browse to the web folder for the Physical Path, set a Host Name ("localhost", or use a licensed URL such as aspdotnetstorefront.*.com and set a HOSTS file entry), and you should be set! Click "Browse localhost..." (or your local URL if used) and verify the site runs.
Install Demo Data (optional)
This part of the install process is optional. The steps below will add about 200 products, some product groups to organize them in your store, and images for the products. We recommend installing this demo data if you are looking for some guidance on how to set up products and product groups or just need to set up a store to quickly try something out.
The SQL script run below clears out several tables in the database before adding data. Do not run this on a database in which you have any data you want to save at this point.
Open SQL Server Management Studio (SSMS) and select the database you created during the install (click on it). Click File -> Open -> File and browse to the DemoData/db folder where you extracted the AspDotNetStorefront software files. Open the 'Install Demo Website Data.sql' file.
Click the Execute button (or press F5) to run the script against your database.
Let the script run to completion. At the bottom of the window you should see a 'Query executed successfully' message. If you see 'Query completed with errors', scroll through the Messages window and find any text in red, and send it to the Support team in a new ticket for assistance.
Navigate to the DemoData/web/images folder on your hard drive, and copy the 2 folders you see there. Then navigate to the /web folder where you installed the software (the same folder where the web.config file lives). Open the /images folder there and paste the 2 folders you copied earlier. If you are prompted to overwrite any files, be sure you know what they are before clicking Yes or OK! If you encounter such a prompt, you likely had set up products previously, and your original images may be lost.
Log into the admin console of your new store and click the 'Refresh Store' button. That's it, you should have products on your store!