Build VirtoCommerce2.6 development environment and keep pace with official Dev branch

VirtoCommerce2.6 was released on December 22, 2015 due to the official addition of some c#6.0 features, and we used the VS2013 development environment (Microsoft has stopped supporting c#6.0 in VS2013), in order to support C # 6.0 it is best to download VS2015 (for the time being not ready for the team to upgrade to VS2015), so the Virtocommerce team submitted issue (details https://github.com/VirtoCommerce/vc-community /issues/197), the Virtocommerce team has been modified in Development Branch Dev.

Because Virtocommerce is currently in a rapid development period, need to develop more work, the result is more bugs, in order to better test and experience virtocommerce the latest development results, decided to stay in sync with the official development branch, so what is the problem, Can submit issue and response in time.

Let me briefly describe the construction process:

1 Open github.com find Virtocommerce and fork

Open GitHub to search for Virtocommerce, or just open https://github.com/VirtoCommerce/vc-community and click the Fork button on the right

Enter your own GitHub warehouse, https://github.com/six006/vc-community (we have no right to operate Virtocommerce official, but after fork we can operate freely under our own project)

2. Configure SSH remote connection and download Virtocommerce remote Dev Branch source code

For SSH configuration, you can go into the group discussion, here is the basic knowledge of git, temporarily not discussed.

Copy what SSH corresponds to

Open Gitextensions->git clone to fill in the relevant clone parameters

Download progress

Download complete

Right-click on "Gitext Browse" and you can see that the branch is dev and the remote branch is Origin/dev

Configuring the operating environment in 3.IIS

Personal habits Use IIS to configure the development environment, and of course you can develop debugging with the default iisexpress of VS

3.1 Modifying the Local host file

Modifying the Host file (C:\WINDOWS\SYSTEM32\DRIVERS\ETC)

Add a domain name map

dev.virtocommerce.cn (for background http://dev.virtocommerce.cn/admin)

store1.virtocommerce.cn (front desk Shop 1)

store2.virtocommerce.cn (front desk Shop 2)

...

3.2 Configuring the front desk (Storefront)

Physical path pointing to "source path \storefront\virtocommerce.storefront"

Add site domain name bindings

3.3 Configuring the Backend (Platform) 3.3.1 Right-click the website "virtocommerce.cn" and clicking "Add Application" admin

Physical path: "Source directory \platform\virtocommerce.platform.web"

3.3.2 Right-click Site "virtocommerce.cn" under "admin", "Add virtual directory" modules

Physical path: "Source directory \platform\modules"

3.3.3 Right-click Site "virtocommerce.cn" under "admin", "Add virtual directory" assets

Physical path: "Source directory \platform\virtocommerce.platform.web\app_data\assets"

Note: If the "source directory \platform\virtocommerce.platform.web\app_data\assets" directory does not exist, you can create a new

3.4 IIS configuration details are as follows

4. Restore Packages 4.1 modified Virtocommerce solution name referenced in Virtocommerce (can not be manipulated)

To differentiate the default solution name for Virtocommerce and to add plugins later, we create our own front and back solution name

Copy VirtoCommerce.Storefront.sln and VirtoCommerce.Manager.sln separately, such as changing the name

Now open the solution, compile error (Expand the project reference, you will find a number of exclamation marks, missing references)

4.2 Open the Vc2.6.storefront.sln solution and restore packages with NuGet

Right-click the solution and select "Enable NuGet package Restore"

4.3 Open the Vc2.6.manager.sln solution and restore packages with NuGet

In addition to those described in 4.2, you can also restore by using the NuGet package for management solution, tools, NuGet Package Manager

5. Modify the front and rear Web. config file

Because we have configured the domain name in IIS to access the site, we need to modify the access path to the related resources in Web. config

At the same time we need to modify the configuration path of the background database

5.1 Modify the configuration file in the foreground vc2.6.storefront/virtocommerce.storefront/web.config

The foreground mainly calls the platform data through the WEBAPI way, so we need to modify the Platform API address, here is Http://dev.virtocommerce.cn/admin

5.2 Modifying the configuration file in platform Vc2.6.manager/virtocommerce.platform.web/web.config

Modify the database connection string, according to the actual situation, you can create a virtocommerce2.6.develop in the database, the user name and password are used SA (production environment do not do so, the simpler the local test, the better)

Modify the resource path, where we set it to Http://dev.virtocommerce.cn/admin/Assets

6. Summary

We set up a local development environment in simple steps, synchronizing with Virtocommerce source (push,pull any play).

Of course, this will involve a problem is how the fork under the project with the original source code to keep in sync, you can add group discussion, in future articles will also be introduced.

Build VirtoCommerce2.6 development environment and keep pace with official Dev branch