Restore with confidence
Resolve Business Central symbols from NuGet and authenticated feeds with deterministic, incremental restores.
Restore symbols, compile dependency-aware workspaces, and validate Business Central packages with one focused tool—from local development to CI.
One package includes all commands: source-impact analysis, translation coverage gates, and machine-readable output. ALWasp is free to use under its license agreement. No license key is necessary.
From zero to verified build
One configuration, every environment
$ dotnet tool install -g left-code.AlWasp
$ alwasp config init
✓ Configuration created
$ alwasp build ci
✓ Symbols restored
✓ 4 projects compiled
✓ Build manifest writtenResolve Business Central symbols from NuGet and authenticated feeds with deterministic, incremental restores.
Compile dependency-aware AL projects from a single configuration with temporary, reversible transforms.
Compare public symbols, validate AppSource compatibility, and emit manifests your CI pipeline can trust.
Learn the workflow
These guides form the core path through a typical ALWasp repository.
Install ALWasp, create alwasp.json, restore symbols, and make your first build in about five minutes.
Install, update, pin, and remove the ALWasp .NET tool.
Understand alwasp.json inventories, profiles, targets, restore settings, transformations, and schema validation.
How ALWasp finds and downloads AL symbol packages: sources, dependency discovery, feed order, version selection, and overrides.
Compile configured targets, discovered project folders, one project, or a VS Code workspace, and control output, rulesets, manifests, and diagnostics.
Run configuration, build, compatibility, and translation gates over one deterministic selection.
Compare compiled AL packages or validate current source against previous packages with AppSourceCop.
Create symbol-only AL apps, pack NuGet dependencies, and explicitly publish to a feed or folder.
Pack a compiled, deployable .app into a NuGet package and push it to a feed for your deployment pipeline.
alwasp analyze — dependency and object graphs, changed objects, public API, and impacted tests from source and git alone.
alwasp validate translations — XLIFF coverage checking, placeholder validation, and release gating.
Prepare translation packages for a translator or an agent, validate the returned XLIFF, and apply it to your apps.
Install the alwasp-translate agent skill for Codex and Claude Code to translate only the XLIFF units that need work.
GitHub Actions and Azure Pipelines patterns for private feeds, manifests, diagnostics, and version application.
Configure public and private NuGet feeds with PATs, feed-token environment mappings, nuget.config, and credential providers.
Operate and extend
Commands, version selection, output formats, exit codes, and problem solutions. See all pages.
All ALWasp commands with their arguments and primary options, with links to the complete option lists and the guides.
How --bc-version and --bc-country select Microsoft symbols, the AL compiler, and analyzers, and which compiler ALWasp uses.
The --format json and ndjson output, the result document, the record stream, and the --result-file option.
The exit codes of all commands, the environment variables that ALWasp reads, and the files and folders that it writes.
Causes and solutions for restore, authentication, compiler, build, and compatibility problems.
What each command does in sequence: restore, config-driven build, version commands, compatibility, source analysis, and translation checks.
Need working code?
Configuration, GitHub Actions, private feeds, versioning, and compatibility gates.
Need a quick answer?
Commands, configuration anatomy, version rules, compatibility, and CI signals.