(Need to make note of SearchIndex config in BareSite folder to point to ConsoleSite SearchIndex folder. Make sure IUSRS has Modify and write permissions as well)
Mediachase offers inside our SDK and full source package a special Sample Site that we call the BareSite implementation. It is designed for two reasons. The first is to make it easier for .NET developers who are familiar with ASP.NET MasterPages to learn our API and implementation of a B2C commerce site; second is to allow customers and partners to use third party CMS systems or to simply deploy web sites without the use of our CMS. In a nutshell, it is a great place to start or a great way to re-use our controls and APIs.
A BareSite (ASP.NET MasterPages Implementation) installation is the ECF running a B2CSampleSite without the Content Management System. If you have your own CMS, you may prefer to use the BareSite instead of the default SDK installation, which contains the ECF Content Management System. There are numerous ways to set up your IIS to support a BareSite installation, but here is one recommended approach (for IIS 6 and above).
It is advisable that you first install the SDK package using the installer.
Note: During the SDK installation, when you get to the IIS Web Site Configuration screen, be sure to create a new IIS Web Site. Do not select the Map to IIS Web Application option. Since you will most likely be installing this in a local development environment (i.e. http://localhost), you will probably specify a "Host name" or a unique port number if you have other sites running on the default port 80. This will give you the base installation of the ECF with its built-in Content Management System. This will make it easier to set up the BareSite.
At the same folder level where you just installed the SDK package, create a new folder called "B2CBareSite." Under this B2CBaresite folder, you will need to move the following folders from your original SDK deployment package:
- B2CBareSite - located in Mediachase.ECF.SDK.5.1.YOURBUILDNUMBER\Data\DeploymentPackage
- ConsoleSite - located in Mediachase.ECF.SDK.5.1.YOURBUILDNUMBER\Data\DeploymentPackage
- Licensing - located in Mediachase.ECF.SDK.5.1.YOURBUILDNUMBER\Data\DeploymentPackage\Mediachase\eCommerceFramework\5.1
- QuartzService - located in Mediachase.ECF.SDK.5.1.YOURBUILDNUMBER\Data\DeploymentPackage\Mediachase\eCommerceFramework\5.1
- Shared - located in Mediachase.ECF.SDK.5.1.YOURBUILDNUMBER\Data\DeploymentPackage\Mediachase\eCommerceFramework\5.1
Note: "_cmsbase" and "_cmsctrls" folders are used only the Content Management System so feel free to delete them.
To update the configuration files, we have provided a program tool called UpdateConfigFIles. The command prompt utility will use the UserProperties.xml (located in Mediachase.ECF.SDK.5.1.YOURBUILDNUMBER\Tools\UpdateConfigFiles) so you will need to change the paths/names based on your new BareSite folder locations.
Set up separate IIS web sites, one for the front-end (B2CBareSite) and another for the back-end (ConsoleSite) and point each to their respective folders.
For the Application Pools, you have two options.
- If you selected the Windows Authentication option during the SDK B2CSampleSite installation, then it is simplest if you point the B2CBareSite Application Pool to the original B2CSampleSite Application Pool.
- If you selected the SQL Authentication option during the SDK B2CSampleSite installation, then you can create a new Application Pool.
For the ConsoleSite, you will need to create a virtual directory called "Apps" and point it to the Shared\Apps folder (at the same level as the B2CBareSite and ConsoleSite folders).
You need to Compile the B2CBareSite.
- Go to B2CBareSite\bin folder and Select All. Then, go to Properties and make all files "Read only." This will prevent these files from being accidentally cleared.
- Go to the B2CBareSite folder and open the B2CBareSite.csproj file in Visual Studio.
- In the Solution Explorer view, right click the very top called "Solution 'B2CBareSite'" and select Build (do not select Rebuild).
- Verify that the Build completes without any errors.
Go to the B2CBareSite's ConsoleSite or Commerce Manager site.
- In the Content Management System > Sites, you will see a B2CSampleSite site definition from the previous SDK B2CSampleSite installation.
- To support a multi-site model, you will need to edit this B2CSampleSite site definition by entering the Public Site URL of the B2CSampleSite.
- Click the Copy icon to create a cloned B2CSampleSite and edit this second site by entering the Public Site URL of the B2CBareSite.
- You should be able to browse both B2CSampleSite and B2CBareSite web sites.