This topic describes the requirements for cloud-compatible software, tools and services used when working with Episerver Digital Experience Cloud Service. This information is useful to ensure that your development environment is compatible with the deployment process and the Azure resources.
Previous knowledge of cloud-based development, and Microsoft Azure in particular, is valuable to get the most out of DXC Service. See Microsoft Azure to learn more.
Note: You can run only one Web Application (ASP.NET Web Application project) in your DXC Service solution. However, you can have unlimited number of sites in that application.
Note: To ensure maximum availability and scaling flexibility, Episerver Find uses dynamic IP ranges. For example, if you require whitelisting of IP addresses in the firewall, make sure that your firewall supports domain-based whitelisting.
The following overview shows the minimum required versions for Episerver products and modules, and tools and services for deploying to the integration environment. See Installing Episerver updates for information about upgrading Episerver solutions.
|Episerver CMS||EPiServer.CMS.UI.Core 11.1.0, EPiServer.CMS.Core 11.2.1||*|
|Episerver Find||EPiServer.Find 13.0.3||*|
|Episerver Commerce||EPiServer.Commerce 11.5.0||*|
|Microsoft Visual Studio||2015||For creating and deploying sites.|
|Episerver CMS Visual Studio extension||11.x||For creating and deploying sites.|
|Microsoft SQL Database||12||For creating bacpac files for database transfers.|
|Microsoft SQL Server Management Studio||12.0.4213.0 (2014 SP1)||For creating bacpac files for database transfers.|
* Only applies to new solutions onboarding DXC Service, does not apply to solutions already on DXC Service.
The following features are not supported within Episerver DXC Service:
You can deploy using deployment tools for a version controlled team development environment, or deploy through Visual Studio using the Episerver extensions and publish profiles. You can use any deployment tool that supports Azure Resource Manager (ARM); see Deploying code changes.
Note: You must install add-on modules to the integration environment through Visual Studio to work with the DXC Service deployment process. Do not change the default configuration that disables users from installing to production.
The following add-ons are not supported in Episerver DXC Service.
Last updated: Sep 19, 2018