# CLI 0.0.4-microsoft-preview.12

Released September 9, 2026. Microsoft migration engine preview; stable `latest` remains 0.0.3.

## Dependency readiness fixes

- When a referenced DLL is not present, look for nested source projects with a matching static `AssemblyName`, including projects whose filenames differ from their assembly names.
- Retain matching project implementations and their transitive source dependencies for migration without requiring the old BizTalk solution to be built first.
- Report `DEPENDENCY_SOURCE_AVAILABLE` with the matching source path instead of a false missing-DLL blocker. Multiple matches remain unverified candidates; binary version/public-key compatibility is not claimed.
- Keep original-project `.snk` signing keys private and excluded from migration evidence. Missing or excluded signing keys no longer block migration analysis.
- Keep loose bindings and other files in unrelated nested solutions out of the selected migration scope unless referenced or explicitly included. Unrelated projects do not introduce readiness blockers.
- Genuine missing dependencies, excluded required source, and missing application binding files still produce actionable errors.

## Verification

- 205 CLI tests passed, including source-producer matching, transitive missing dependencies, exclusions, ambiguous matches, signing keys, and unrelated nested-solution artifacts.
- Read-only FINACCONT-BT source-readiness check: two blockers reduced to zero; nine relevant projects retained and 24 unrelated projects ignored.
- No full customer conversion or Azure deployment was performed. Source readiness is not proof of successful orchestration conversion or runtime compatibility.

## Update in PowerShell

```powershell
Invoke-WebRequest 'https://tools.lambogenius.com/lambogenius-integration-migration/0.0.4-microsoft-preview.12/install-cli.ps1' -OutFile install-cli-preview12.ps1
# Review the downloaded script before running it.
& .\install-cli-preview12.ps1 -SkipDependencies
li.cmd --version
```

Omit `-SkipDependencies` if prerequisites also need installation. Use `li.cmd` in
PowerShell because `li` can resolve to the built-in `Get-ChildItem` alias.
Finish any running migration before updating. Preserve previous generated output;
use a fresh generated workspace if a changed scope or engine fingerprint prevents
checkpoint reuse. Do not edit checkpoint fingerprints to bypass validation.