Copy page

PowerShell Module

PowerShell module

The businessdev.ALbuild PowerShell module is the engine of ALbuild, organised into nine use-case modules. Both the Azure DevOps extension and the VS Code extension are thin shells over it, so everything the toolchain can do is available here as plain PowerShell.

• Version: see the PowerShell Gallery
• Requires: PowerShell 5.1 or 7+ (dual-target)
• Packaging: one Gallery package, one version, composed of use-case nested modules.

---

Installation

Code
# install once: one package, all areas
Install-Module businessdev.ALbuild -Scope CurrentUser
Import-Module businessdev.ALbuild

# confirm
Get-Command -Module businessdev.ALbuild

---

Module reference

Module	Tier	What it covers
Core	Free	Config, logging, licensing, version math, project config, build order, version stamping, readable errors
Containers	Free	Artifacts, Docker container lifecycle, users, test toolkit, config packages, Traefik, certificates
Apps	Free (except AppSource validation)	Compile, publish/sync/install/unpublish, sign, test, coverage, app version, 365 apps, XLIFF
Feeds	Free	Dependency resolver, dependency reconciliation, feed providers, NuGet packaging, feed-view promotion
RuntimePackages	Licensed	The runtime-package factory: plan by platform version, worker pool, checkpointing
Marketplace	Licensed	AppSource / Partner Center ingestion
OnPrem	Licensed	On-prem publish/install/sync/upgrade, PTE, Dev
Environments	Licensed	Demo/dev environment provisioning
Pipeline	Free	Local pipeline runner

Each module page is generated from the cmdlets' own comment-based help, so it always lists the complete set as shipped.

Licensed cmdlets call Assert-ALbuildLicensed on entry. See Licensing & tiers.

---

How the reference pages are organised

Each module page opens with a table of its cmdlets, then documents every cmdlet in full:

• Synopsis & description: what it does and the important behaviour.
• Syntax: the parameter signature.
• Parameters: a table with type, whether it is required, allowed values, defaults and a description.
• Output: what the cmdlet returns.
• Examples: worked invocations.

---

Common workflows

• Build & test an app → Find-BcArtifactUrl → New-BcContainer → Resolve-BcDependencies → Invoke-BcCompiler → Publish-BcContainerApp → Invoke-BcContainerTest → Remove-BcContainer.
• Sign & package → Invoke-BcAppSigning → New-BcNuGetPackage → Publish-BcPackage.
• Deploy (licensed) → Publish-BcPerTenantExtension / Publish-BcOnPremApp / Submit-BcMarketplaceApp.
• Measure coverage & test quality → Convert-BcCodeCoverage → Test-BcCodeCoverageThreshold / Get-BcCodeCoverageDelta / Get-BcTestQuality. See Code coverage.
• Build runtime packages (licensed) → Get-BcRuntimeWorkSet → Invoke-BcRuntimeFactory. See Runtime packages.
• Reproduce a pipeline locally → Invoke-ALbuildPipeline.