Deep Dive on

Commerce
Extension Packaging
and Azure DevOps
Build Pipeline Setup

Luke Graham
Mugunthan Mani
1
Dynamics 365 Product
guidance
Implementation Guide General Case
guidance studies
Collective experience gained through
thousands of Dynamics 365 implementations

References to Guide Checklists

other guidance Experience

Highlights Recommended
deliverables
Conceptual
graphic
support

Available at: https://aka.ms/d365implementationguide

2
Agenda
❑ Commerce Extension Package overview.
❑ Packaging Projects.
❑ Merge CSU packages.
❑ Setup Build/CICD Pipeline.
❑ Signing the installers and appx.
❑ Setup VS 2017 Build agent for MPOS in build VMs
❑ Session Takeaways
❑ Q & A.

3
Commerce Extension Package overview.

4
COMPILATION

EXTENSION PACKAGING OVERVIEW

COMPILATION

COMMERCE SCALE UNIT HEADLESS COMMERCE MODERN POS SHARED HWS

DEPLOYMENT CLOUD-HOSTED ON-PREM INSTALLER ON-PREM INSTALLER ON-PREM INSTALLER
Azure Web App / Azure SQL
Commerce Runtime Commerce Runtime

HEADLESS COMMERCE Channel Database Schema Channel Database Schema HWS Runtime
EXTENSION PACKAGE
POS UI & Runtime POS UI & Runtime

POS UI & Runtime Extension HEADLESS COMMERCE MODERN POS SHARED HWS
EXTENSION PACKAGE EXTENSION PACKAGE EXTENSION PACKAGE
Runtime / API Extension UI / Runtime / API Extension
Runtime / API Extension

Database Extension Database Extension Hardware Extension

Database Extension
DEPLOYMENT POS UI & Runtime Extension POS UI & Runtime Extension

DYNAMICS 365 LIFE CYCLE SERVICES ON-PREM MASS DEPLOYMENT INFRASTRUCTURE

MICROSOFT OWNED AND MANAGED CUSTOMER OWNED AND MANAGED

DEPLOYMENT & SERVICING EXPERIENCE

5
Commerce Sdk Project & Package Types
Package Type Extension Description Project Commerce SDK Nuget Package Package Format/Output Type Multiple
Components Type Extension
Packages
Support
Commerce Scale CRT The package that is .NET SDK Microsoft.Dynamics.Commerce.Sdk.ScaleUn .zip file containing the contents No
Unit Cloud API uploaded to LCS to deploy csproj it of the Commerce Scale Unit
Extension Database Commerce Scale Unit (netstandar Extension package.
Package CPOS extensions to Commerce d2.0)
Scale Units hosted in the
cloud.
Commerce Scale CRT The installer for extensions .NET SDK Microsoft.Dynamics.Commerce.Sdk.Installer .exe installer that will Yes
Unit Self Hosted API for self hosted CSU csproj s.ScaleUnit install/uninstall the CSU
Extensions Database instances. (net461) extensions for self hosted CSU
Installer CPOS deployments

Modern POS CRT The installer for Modern .NET SDK Microsoft.Dynamics.Commerce.Sdk.Installer .exe installer that will Yes
Extension API POS extension packages csproj s.ModernPos install/uninstall the Modern POS
Package Installer Database including extensions for (net461) extensions
MPOS dedicated hardware station
and offline
Shared Hardware HWS The installer for Shared .NET SDK Microsoft.Dynamics.Commerce.Sdk.Installer .exe installer that will Yes
Station Extension Hardware Station Extensions csproj s.HardwareStation install/uninstall the hardware
Package Installer (net461) station extensions for shared
hardware station installs (IIS)

6
Demo: Commerce Extension Packaging projects and
ISV package merge during build.

7
Commerce Build pipeline and Signing the package:
❑ Setup the pipeline.

❑ Sign the MPOS appx.

❑ Sign the installers.

8
Demo – Build pipeline and Sign the package.

9
Setup VS 2017 Build Agent.

10
Background Info
 Visual Studio 2017 is required to build MPOS
 Azure DevOps is removing support for Visual Studio 2017 hosted
agents
 Use a self hosted agent to build MPOS Extensions
 Additional Resources
 Getting started with POS extensions - Commerce | Dynamics 365 | Microsoft Docs
 Deploy an Azure Pipelines agent on Windows - Azure Pipelines | Microsoft Docs

11
Step 1: Create a new VM in Azure

• Go to the Azure Portal and create a new VM to be used as the build agent
• Use the Windows Server 2022 Datacenter Image

12
Step 2: Install Visual
Studio 2017 on the
VM

13
Step 3: Install .NET Core
3.1 SDK and .NET
Framework 4.7.2

14
Step 4: Create a personal access token for the agent

15
Step 5: Configure the Agent

Download the agent (on the Azure VM) Configure the agent from Powershell

16
Step 6: Use the agent to run the ADO pipeline

Verify that the agent was successfully added to the Update the pipeline for your repo to use the
“Default” agent pool in your organization “Default” agent pool

17
Key Takeaways
❑ Packaging Projects.
❑ Independent packaging for On-prem components.
❑ Merge ISVs Extension packages for CSU.
❑ VS 2017 Build agent for MPOS.

18
Upcoming Tech talks
Tech talk title Date Persona

Hardware Station Extension deep dive with the
Commerce SDK
Migrate Commerce Runtime and Headless
Commerce (Retail Server) extension to the
Commerce SDK
Jan 12th Deep dive on how to customize the Hardware Developer, Technical
station (HWS) to integrate with Payment terminal or consultant and Architect.
hardware device with Commerce SDK.
Jan 26th or 27th Learn how to migrate the Commerce runtime and Developer, Technical
TBD Headless Commerce extension to the Commerce consultant and Architect.
SDK.

19
Q&A

20