Son Do
May 26, 2015
visibility 2962
star star star star star
(2 votes)

New way to create Azure Commerce site in 8.12.0

EPiServer.Commerce 8.12.0 was released and it includes new way to create new EPiServer Commerce site that’s Azure compatible.

We just need to do some simple steps:

  • Open Visual Studio, select Tools > Extensions and Updates menu. In the dialog, select Online and Search EPiServer CMS Visual Studio Extension then install extenstion.
  • Create a new project by selecting New > Project > Visual C#, and then EPiServer > EPiServer Web Site. In the dialog select Empty, uncheck "Add EPiServer Search".
  • Install the NuGet package EPiServer.Commerce, to 8.12 at least.
  • Install the NuGet package EPiServer.Commerce.Azure to the project.
  • Remember that run update-epidatabase in Package Manager Console.

Now we have a new site that compatible with Azure and ready for Azure deployment.

Refer to http://world.episerver.com/documentation/Items/Developers-Guide/EPiServer-Commerce/8/Deployment/deploying-commerce-to-azure-web-apps/ to deploy it to Azure Web Apps
May 26, 2015

Comments

Frederik Vig
Frederik Vig May 26, 2015 02:02 PM

How about the Commerce Manager?

Son Do
Son Do May 28, 2015 08:30 AM

Hi Frederik, 

To get new Commerce Manager site, we can download this one and following some steps below:

- Copy configuration files from front-end site to root folder of Commerce Manager project .

Update the EPiServer.CommerceManager package to the latest version (or 8.0 at least, refer to Commerce-specific updating steps, section Updating Commerce Manager)

- Install Azure package to Commerce Manager using nuget package EPiServer.CommerceManager.Azure (refer to Upgrading and deploying Commerce to Azure, step 2 - Upgrading NuGet packages and make the site ready for Azure)

- Apply your Azure configuration.

So Commerce Manager site is ready for deployment.

/Son Do

May 28, 2015 08:41 AM

An easier way of installing Commerce Manager is to create a new ASP.Net Web Application in the same solution as the front-end site. Then you just have to add the nuget package EPiServer.CommerceManager.Azure to the empty web site to convert it to a commerce manager site ready for Azure.

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |