This topic describes how to create code packages when deploying through the Deployment API for Episerver Customer-Centric Digital Experience Platform (DXP).
The first step to use the API is to bundle your web application into a code package. Use the following conventions when you name a code package (a package containing web app binaries, configuration and so on).
<app name>.<package type>.app.<version>.nupkg
customer.cms.app.1.0.0.nupkg ("customer" being the "app name")
commerce.app.20190311103000.nupkg (version defined in a date/time format)
The package should contain the web app-related files, which normally exists at the path D:\Home\Site on the actual Azure Web App.
Only folders and files related to the code are allowed (that is, wwwroot, applicationHost.xdt), except for a metadata file (optional) that should follow the package name.
Sample folder structure
Transforms in any target environment needs to be a part of the initial code package.
You can download an Alloy package example here: alloy.cms.app.1.2.1.nupkg
You can create a package by deploying to a folder and zipping this folder.
Example using MSBuild:
You can zip this folder (SitePackageContent in the example) as cms.app.1.0.0.nupkg to make it a deployment package that you can use in DXP.
Last updated: Oct 17, 2019