From 3105a64a4e0ca096e7e87885ab4954abc7ff9b83 Mon Sep 17 00:00:00 2001 From: adamwroo Date: Tue, 15 Feb 2022 11:27:25 +0100 Subject: [PATCH] additional step for generating an Azure package added in 'Creating a release' doc --- be/docs/README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/be/docs/README.md b/be/docs/README.md index 0451754..34e0b94 100644 --- a/be/docs/README.md +++ b/be/docs/README.md @@ -158,6 +158,13 @@ ConvertTo-SCModuleWebDeployPackage "\UrlMapper2_CD ConvertTo-SCModuleWebDeployPackage "\UrlMapper2_CM-.zip" "" ``` +> Packages generated by Sitecore Azure Toolkit don't really follow the Microsoft standards in the `parameters.xml` file, since they define a `Application Path` parameter containing the application name instead of the standard `IIS Web Application Name` parameters. In order to make the packages work with the default IIS Deployment and Azure App Service deployment tasks, the `parameters.xml` needs to be adjusted accordingly and injected into the packages. + +You can adjust the `parameters.xml` using the `Update-SCWebDeployPackage` cmdlet as follows: +```powershell +Update-SCWebDeployPackage -Path "" -ParametersXmlPath "" +``` + Please note that if you are planning to use the modules for local or on-prem installations, you will have to disable dacpac options, which can be accomplished as follows: ```powershell